Uplink Transmission Cancellation

ABSTRACT

A wireless device receives, from a base station, a first uplink grant, for a first transport block (TB) of a hybrid acknowledgment repeat request (HARQ) process. The wireless device cancels an uplink transmission of the first TB of the HARQ process based on receiving a pre-emption indication indicating cancellation of transmission via one or more uplink resources indicated by the first uplink grant. The wireless device determines, after cancelling the uplink transmission of the first TB of the HARQ process, that a received second uplink grant is used for a new transmission of a second TB associated with the HARQ process. The wireless device transmits, to the base station, the second TB of the HARQ process based on the determining.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/US2020/018354, filed Feb. 14, 2020, which claims the benefit of U.S.Provisional Application No. 62/805,894, filed Feb. 14, 2019, which ishereby incorporated by reference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 2A is a diagram of an example user plane protocol stack as per anaspect of an embodiment of the present disclosure.

FIG. 2B is a diagram of an example control plane protocol stack as peran aspect of an embodiment of the present disclosure.

FIG. 3 is a diagram of an example wireless device and two base stationsas per an aspect of an embodiment of the present disclosure.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals as per an aspect of an embodiment of the presentdisclosure.

FIG. 5B is a diagram of an example downlink channel mapping and exampledownlink physical signals as per an aspect of an embodiment of thepresent disclosure.

FIG. 6 is a diagram depicting an example transmission time or receptiontime for a carrier as per an aspect of an embodiment of the presentdisclosure.

FIG. 7A and FIG. 7B are diagrams depicting example sets of OFDMsubcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 8 is a diagram depicting example OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 9A is a diagram depicting an example CSI-RS and/or SS blocktransmission in a multi-beam system.

FIG. 9B is a diagram depicting an example downlink beam managementprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram of configured BWPs as per an aspect of anembodiment of the present disclosure.

FIG. 11A, and FIG. 11B are diagrams of an example multi connectivity asper an aspect of an embodiment of the present disclosure.

FIG. 12 is a diagram of an example random access procedure as per anaspect of an embodiment of the present disclosure.

FIG. 13 is a structure of example MAC entities as per an aspect of anembodiment of the present disclosure.

FIG. 14 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 15 is a diagram of example RRC states as per an aspect of anembodiment of the present disclosure.

FIG. 16A, FIG. 16B and FIG. 16C are examples of MAC subheaders as per anaspect of an embodiment of the present disclosure.

FIG. 17A and FIG. 17B are examples of MAC PDUs as per an aspect of anembodiment of the present disclosure.

FIG. 18 is an example of LCIDs for DL-SCH as per an aspect of anembodiment of the present disclosure.

FIG. 19 is an example of LCIDs for UL-SCH as per an aspect of anembodiment of the present disclosure.

FIG. 20A is an example of an SCell Activation/Deactivation MAC CE of oneoctet as per an aspect of an embodiment of the present disclosure.

FIG. 20B is an example of an SCell Activation/Deactivation MAC CE offour octets as per an aspect of an embodiment of the present disclosure.

FIG. 21A is an example of an SCell hibernation MAC CE of one octet asper an aspect of an embodiment of the present disclosure.

FIG. 21B is an example of an SCell hibernation MAC CE of four octets asper an aspect of an embodiment of the present disclosure.

FIG. 21C is an example of MAC control elements for an SCell statetransitions as per an aspect of an embodiment of the present disclosure.

FIG. 22 is an example of DCI formats as per an aspect of an embodimentof the present disclosure.

FIG. 23 is an example of BWP management on an SCell as per an aspect ofan embodiment of the present disclosure.

FIG. 24 is an example DRX operation as per an aspect of an embodiment ofthe present disclosure.

FIG. 25 is an example DRX operation as per an aspect of an embodiment ofthe present disclosure.

FIG. 26 is an example HARQ operation as per an aspect of an embodimentof the present disclosure.

FIG. 27 is an example HARQ operation as per an aspect of an embodimentof the present disclosure.

FIG. 28 is an example uplink pre-emption mechanism as per an aspect ofan embodiment of the present disclosure.

FIG. 29 is an example uplink pre-emption mechanism as per an aspect ofan embodiment of the present disclosure.

FIG. 30 is an example uplink pre-emption mechanism as per an aspect ofan embodiment of the present disclosure.

FIG. 31 is an example improved HARQ operation when uplink pre-emption issupported as per an aspect of an embodiment of the present disclosure.

FIG. 32 is an example improved HARQ operation when uplink pre-emption issupported as per an aspect of an embodiment of the present disclosure.

FIG. 33 is an example improved HARQ operation when uplink pre-emption issupported as per an aspect of an embodiment of the present disclosure.

FIG. 34 is an example improved HARQ operation when uplink pre-emption issupported as per an aspect of an embodiment of the present disclosure.

FIG. 35 is an example improved BWP operation when uplink pre-emption issupported as per an aspect of an embodiment of the present disclosure.

FIG. 36 is an example improved BWP operation when uplink pre-emption issupported as per an aspect of an embodiment of the present disclosure.

FIG. 37 is an example improved DRX operation when uplink pre-emption issupported as per an aspect of an embodiment of the present disclosure.

FIG. 38 is an example improved HARQ processing when out-of-order HARQ issupported as per an aspect of an embodiment of the present disclosure.

FIG. 39 is an example improved HARQ processing when out-of-order HARQ issupported as per an aspect of an embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable uplink pre-emptionoperation of a wireless device and/or a base station. Embodiments of thetechnology disclosed herein may be employed in the technical field ofmulticarrier communication systems. More particularly, the embodimentsof the technology disclosed herein may relate to a wireless deviceand/or a base station in a multicarrier communication system.

The following Acronyms are used throughout the present disclosure:

3GPP 3rd Generation Partnership Project 5GC 5G Core Network ACKAcknowledgement AMF Access and Mobility Management Function ARQAutomatic Repeat Request AS Access Stratum ASIC Application-SpecificIntegrated Circuit BA Bandwidth Adaptation BCCH Broadcast ControlChannel BCH Broadcast Channel BPSK Binary Phase Shift Keying BWPBandwidth Part CA Carrier Aggregation CC Component Carrier CCCH CommonControl CHannel CDMA Code Division Multiple Access CN Core Network CPCyclic Prefix CP-OFDM Cyclic Prefix-Orthogonal Frequency DivisionMultiplex C-RNTI Cell-Radio Network Temporary Identifier CS ConfiguredScheduling CSI Channel State Information CSI-RS Channel StateInformation-Reference Signal CQI Channel Quality Indicator CRC CyclicRedundancy Check CSS Common Search Space CU Central Unit DAI DownlinkAssignment Index DC Dual Connectivity DCCH Dedicated Control Channel DCIDownlink Control Information DL Downlink DL-SCH Downlink Shared CHannelDM-RS DeModulation Reference Signal DRB Data Radio Bearer DRXDiscontinuous Reception DTCH Dedicated Traffic Channel DU DistributedUnit EPC Evolved Packet Core E-UTRA Evolved UMTS Terrestrial RadioAccess E-UTRAN Evolved-Universal Terrestrial Radio Access Network FDDFrequency Division Duplex FPGA Field Programmable Gate Arrays F1-CF1-Control plane F1-U F1-User plane gNB next generation Node B HARQHybrid Automatic Repeat reQuest HDL Hardware Description Languages IEInformation Element IP Internet Protocol LCID Logical Channel IdentifierLTE Long Term Evolution MAC Media Access Control MCG Master Cell GroupMCS Modulation and Coding Scheme MeNB Master evolved Node B MIB MasterInformation Block MME Mobility Management Entity MN Master Node NACKNegative Acknowledgement NAS Non-Access Stratum NG CP Next GenerationControl Plane NGC Next Generation Core NG-C NG-Control plane ng-eNB nextgeneration evolved Node B NG-U NG-User plane NR New Radio NR MAC NewRadio MAC NR PDCP New Radio PDCP NR PHY New Radio PHYsical NR RLC NewRadio RLC NR RRC New Radio RRC NSSAI Network Slice Selection AssistanceInformation O&M Operation and Maintenance OFDM orthogonal FrequencyDivision Multiplexing PBCH Physical Broadcast CHannel PCC PrimaryComponent Carrier PCCH Paging Control CHannel PCell Primary Cell PCHPaging CHannel PDCCH Physical Downlink Control CHannel PDCP Packet DataConvergence Protocol PDSCH Physical Downlink Shared CHannel PDU ProtocolData Unit PHICH Physical HARQ Indicator CHannel PHY PHYsical PLMN PublicLand Mobile Network PMI Precoding Matrix Indicator PRACH Physical RandomAccess CHannel PRB Physical Resource Block PSCell Primary Secondary CellPSS Primary Synchronization Signal pTAG primary Timing Advance GroupPT-RS Phase Tracking Reference Signal PUCCH Physical Uplink ControlCHannel PUSCH Physical Uplink Shared CHannel QAM Quadrature AmplitudeModulation QFI Quality of Service Indicator QoS Quality of Service QPSKQuadrature Phase Shift Keying RA Random Access RACH Random AccessCHannel RAN Radio Access Network RAT Radio Access Technology RA-RNTIRandom Access-Radio Network Temporary Identifier RB Resource Blocks RBGResource Block Groups RI Rank indicator RLC Radio Link Control RLM RadioLink Monitoring RNTI Radio Network Temporary Identifier RRC RadioResource Control RRM Radio Resource Management RS Reference Signal RSRPReference Signal Received Power SCC Secondary Component Carrier SCellSecondary Cell SCG Secondary Cell Group SC-FDMA Single Carrier-FrequencyDivision Multiple Access SDAP Service Data Adaptation Protocol SDUService Data Unit SeNB Secondary evolved Node B SFN System Frame NumberS-GW Serving GateWay SI System Information SIB System Information BlockSMF Session Management Function SN Secondary Node SpCell Special CellSRB Signaling Radio Bearer SRS Sounding Reference Signal SSSynchronization Signal SSS Secondary Synchronization Signal sTAGsecondary Timing Advance Group TA Timing Advance TAG Timing AdvanceGroup TAI Tracking Area Identifier TAT Time Alignment Timer TB TransportBlock TCI Transmission Configuration Indication TC-RNTI TemporaryCell-Radio Network Temporary Identifier TDD Time Division Duplex TDMATime Division Multiple Access TRP Transmission Reception Point TTITransmission Time Interval UCI Uplink Control Information UE UserEquipment UL Uplink UL-SCH Uplink Shared CHannel UPF User Plane FunctionUPGW User Plane Gateway VHDL VHSIC Hardware Description Language Xn-CXn-Control plane Xn-U Xn-User plane

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but not limited to: Code DivisionMultiple Access (CDMA), Orthogonal Frequency Division Multiple Access(OFDMA), Time Division Multiple Access (TDMA), Wavelet technologies,and/or the like. Hybrid transmission mechanisms such as TDMA/CDMA, andOFDM/CDMA may also be employed. Various modulation schemes may beapplied for signal transmission in the physical layer. Examples ofmodulation schemes include, but are not limited to: phase, amplitude,code, a combination of these, and/or the like. An example radiotransmission method may implement Quadrature Amplitude Modulation (QAM)using Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying(QPSK), 16-QAM, 64-QAM, 256-QAM, 1024-QAM, and/or the like. Physicalradio transmission may be enhanced by dynamically or semi-dynamicallychanging the modulation and coding scheme depending on transmissionrequirements and radio conditions.

FIG. 1 is an example Radio Access Network (RAN) architecture as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, a RAN node may be a next generation Node B (gNB) (e.g.120A, 120B) providing New Radio (NR) user plane and control planeprotocol terminations towards a first wireless device (e.g. 110A). In anexample, a RAN node may be a next generation evolved Node B (ng-eNB)(e.g. 120C, 120D), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device (e.g. 110B). The first wireless device maycommunicate with a gNB over a Uu interface. The second wireless devicemay communicate with a ng-eNB over a Uu interface.

A gNB or an ng-eNB may host functions such as radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of UEs inRRC_INACTIVE state, distribution function for Non-Access Stratum (NAS)messages, RAN sharing, dual connectivity or tight interworking betweenNR and E-UTRA.

In an example, one or more gNB s and/or one or more ng-eNB s may beinterconnected with each other by means of Xn interface. A gNB or anng-eNB may be connected by means of NG interfaces to 5G Core Network(5GC). In an example, 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g. 130A or 130B). A gNB or an ng-eNB may beconnected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g. non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide functions such asNG interface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer or warning message transmission.

In an example, a UPF may host functions such as anchor point forintra-/inter-Radio Access Technology (RAT) mobility (when applicable),external PDU session point of interconnect to data network, packetrouting and forwarding, packet inspection and user plane part of policyrule enforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, QoS handling for user plane, e.g. packetfiltering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplinktraffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

In an example, an AMF may host functions such as NAS signalingtermination, NAS signaling security, Access Stratum (AS) securitycontrol, inter Core Network (CN) node signaling for mobility between3^(rd) Generation Partnership Project (3GPP) access networks, idle modeUE reachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (subscription and policies),support of network slicing and/or Session Management Function (SMF)selection.

FIG. 2A is an example user plane protocol stack, where Service DataAdaptation Protocol (SDAP) (e.g. 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g. 212 and 222), Radio Link Control (RLC) (e.g. 213and 223) and Media Access Control (MAC) (e.g. 214 and 224) sublayers andPhysical (PHY) (e.g. 215 and 225) layer may be terminated in wirelessdevice (e.g. 110) and gNB (e.g. 120) on the network side. In an example,a PHY layer provides transport services to higher layers (e.g. MAC, RRC,etc). In an example, services and functions of a MAC sublayer maycomprise mapping between logical channels and transport channels,multiplexing/demultiplexing of MAC Service Data Units (SDUs) belongingto one or different logical channels into/from Transport Blocks (TBs)delivered to/from the PHY layer, scheduling information reporting, errorcorrection through Hybrid Automatic Repeat request (HARQ) (e.g. one HARQentity per carrier in case of Carrier Aggregation (CA)), priorityhandling between UEs by means of dynamic scheduling, priority handlingbetween logical channels of one UE by means of logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. In an example, mappingrestrictions in a logical channel prioritization may control whichnumerology and/or transmission timing a logical channel may use. In anexample, an RLC sublayer may supports transparent mode (TM),unacknowledged mode (UM) and acknowledged mode (AM) transmission modes.The RLC configuration may be per logical channel with no dependency onnumerologies and/or Transmission Time Interval (TTI) durations. In anexample, Automatic Repeat Request (ARQ) may operate on any of thenumerologies and/or TTI durations the logical channel is configuredwith. In an example, services and functions of the PDCP layer for theuser plane may comprise sequence numbering, header compression anddecompression, transfer of user data, reordering and duplicatedetection, PDCP PDU routing (e.g. in case of split bearers),retransmission of PDCP SDUs, ciphering, deciphering and integrityprotection, PDCP SDU discard, PDCP re-establishment and data recoveryfor RLC AM, and/or duplication of PDCP PDUs. In an example, services andfunctions of SDAP may comprise mapping between a QoS flow and a dataradio bearer. In an example, services and functions of SDAP may comprisemapping Quality of Service Indicator (QFI) in DL and UL packets. In anexample, a protocol entity of SDAP may be configured for an individualPDU session.

FIG. 2B is an example control plane protocol stack where PDCP (e.g. 233and 242), RLC (e.g. 234 and 243) and MAC (e.g. 235 and 244) sublayersand PHY (e.g. 236 and 245) layer may be terminated in wireless device(e.g. 110) and gNB (e.g. 120) on a network side and perform service andfunctions described above. In an example, RRC (e.g. 232 and 241) may beterminated in a wireless device and a gNB on a network side. In anexample, services and functions of RRC may comprise broadcast of systeminformation related to AS and NAS, paging initiated by 5GC or RAN,establishment, maintenance and release of an RRC connection between theUE and RAN, security functions including key management, establishment,configuration, maintenance and release of Signaling Radio Bearers (SRBs)and Data Radio Bearers (DRBs), mobility functions, QoS managementfunctions, UE measurement reporting and control of the reporting,detection of and recovery from radio link failure, and/or NAS messagetransfer to/from NAS from/to a UE. In an example, NAS control protocol(e.g. 231 and 251) may be terminated in the wireless device and AMF(e.g. 130) on a network side and may perform functions such asauthentication, mobility management between a UE and a AMF for 3GPPaccess and non-3GPP access, and session management between a UE and aSMF for 3GPP access and non-3GPP access.

In an example, a base station may configure a plurality of logicalchannels for a wireless device. A logical channel in the plurality oflogical channels may correspond to a radio bearer and the radio bearermay be associated with a QoS requirement. In an example, a base stationmay configure a logical channel to be mapped to one or moreTTIs/numerologies in a plurality of TTIs/numerologies. The wirelessdevice may receive a Downlink Control Information (DCI) via PhysicalDownlink Control CHannel (PDCCH) indicating an uplink grant. In anexample, the uplink grant may be for a first TTI/numerology and mayindicate uplink resources for transmission of a transport block. Thebase station may configure each logical channel in the plurality oflogical channels with one or more parameters to be used by a logicalchannel prioritization procedure at the MAC layer of the wirelessdevice. The one or more parameters may comprise priority, prioritizedbit rate, etc. A logical channel in the plurality of logical channelsmay correspond to one or more buffers comprising data associated withthe logical channel. The logical channel prioritization procedure mayallocate the uplink resources to one or more first logical channels inthe plurality of logical channels and/or one or more MAC ControlElements (CEs). The one or more first logical channels may be mapped tothe first TTI/numerology. The MAC layer at the wireless device maymultiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logicalchannel) in a MAC PDU (e.g., transport block). In an example, the MACPDU may comprise a MAC header comprising a plurality of MAC sub-headers.A MAC sub-header in the plurality of MAC sub-headers may correspond to aMAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/orone or more MAC SDUs. In an example, a MAC CE or a logical channel maybe configured with a Logical Channel IDentifier (LCID). In an example,LCID for a logical channel or a MAC CE may be fixed/pre-configured. Inan example, LCID for a logical channel or MAC CE may be configured forthe wireless device by the base station. The MAC sub-headercorresponding to a MAC CE or a MAC SDU may comprise LCID associated withthe MAC CE or the MAC SDU.

In an example, a base station may activate and/or deactivate and/orimpact one or more processes (e.g., set values of one or more parametersof the one or more processes or start and/or stop one or more timers ofthe one or more processes) at the wireless device by employing one ormore MAC commands. The one or more MAC commands may comprise one or moreMAC control elements. In an example, the one or more processes maycomprise activation and/or deactivation of PDCP packet duplication forone or more radio bearers. The base station may transmit a MAC CEcomprising one or more fields, the values of the fields indicatingactivation and/or deactivation of PDCP duplication for the one or moreradio bearers. In an example, the one or more processes may compriseChannel State Information (CSI) transmission of on one or more cells.The base station may transmit one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells. Inan example, the one or more processes may comprise activation ordeactivation of one or more secondary cells. In an example, the basestation may transmit a MA CE indicating activation or deactivation ofone or more secondary cells. In an example, the base station maytransmit one or more MAC CEs indicating starting and/or stopping one ormore Discontinuous Reception (DRX) timers at the wireless device. In anexample, the base station may transmit one or more MAC CEs indicatingone or more timing advance values for one or more Timing Advance Groups(TAGs).

FIG. 3 is a block diagram of base stations (base station 1, 120A, andbase station 2, 120B) and a wireless device 110. A wireless device maybe called an UE. A base station may be called a NB, eNB, gNB, and/orng-eNB. In an example, a wireless device and/or a base station may actas a relay node. The base station 1, 120A, may comprise at least onecommunication interface 320A (e.g. a wireless modem, an antenna, a wiredmodem, and/or the like), at least one processor 321A, and at least oneset of program code instructions 323A stored in non-transitory memory322A and executable by the at least one processor 321A. The base station2, 120B, may comprise at least one communication interface 320B, atleast one processor 321B, and at least one set of program codeinstructions 323B stored in non-transitory memory 322B and executable bythe at least one processor 321B.

A base station may comprise many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may comprise many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At Radio Resource Control (RRC)connection establishment/re-establishment/handover, one serving cell mayprovide the NAS (non-access stratum) mobility information (e.g. TrackingArea Identifier (TAI)). At RRC connection re-establishment/handover, oneserving cell may provide the security input. This cell may be referredto as the Primary Cell (PCell). In the downlink, a carrier correspondingto the PCell may be a DL Primary Component Carrier (PCC), while in theuplink, a carrier may be an UL PCC. Depending on wireless devicecapabilities, Secondary Cells (SCells) may be configured to formtogether with a PCell a set of serving cells. In a downlink, a carriercorresponding to an SCell may be a downlink secondary component carrier(DL SCC), while in an uplink, a carrier may be an uplink secondarycomponent carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to one cell. The cell ID or cell index may alsoidentify the downlink carrier or uplink carrier of the cell (dependingon the context it is used). In the disclosure, a cell ID may be equallyreferred to a carrier ID, and a cell index may be referred to a carrierindex. In an implementation, a physical cell ID or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted on a downlink carrier. A cell index may be determinedusing RRC messages. For example, when the disclosure refers to a firstphysical cell ID for a first downlink carrier, the disclosure may meanthe first physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.When the disclosure indicates that a first carrier is activated, thespecification may equally mean that a cell comprising the first carrieris activated.

A base station may transmit to a wireless device one or more messages(e.g. RRC messages) comprising a plurality of configuration parametersfor one or more cells. One or more cells may comprise at least oneprimary cell and at least one secondary cell. In an example, an RRCmessage may be broadcasted or unicasted to the wireless device. In anexample, configuration parameters may comprise common parameters anddedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SIs.The minimum SI may be periodically broadcast. The minimum SI maycomprise basic information required for initial access and informationfor acquiring any other SI broadcast periodically or provisionedon-demand, i.e. scheduling information. The other SI may either bebroadcast, or be provisioned in a dedicated manner, either triggered bya network or upon request from a wireless device. A minimum SI may betransmitted via two different downlink channels using different messages(e.g. MasterInformationBlock and SystemInformationBlockType1). AnotherSI may be transmitted via SystemInformationBlockType2. For a wirelessdevice in an RRC_Connected state, dedicated RRC signalling may beemployed for the request and delivery of the other SI. For the wirelessdevice in the RRC_Idle state and/or the RRC_Inactive state, the requestmay trigger a random-access procedure.

A wireless device may report its radio access capability informationwhich may be static. A base station may request what capabilities for awireless device to report based on band information. When allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

When CA is configured, a wireless device may have an RRC connection witha network. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. When adding a new SCell,dedicated RRC signalling may be employed to send all required systeminformation of the SCell i.e. while in connected mode, wireless devicesmay not need to acquire broadcasted system information directly from theSCells.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells and cell groups). As part of the RRCconnection reconfiguration procedure, NAS dedicated information may betransferred from the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be to establish (or reestablish, resume) an RRC connection. an RRCconnection establishment procedure may comprise SRB1 establishment. TheRRC connection establishment procedure may be used to transfer theinitial NAS dedicated information/message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure after successful security activation. Ameasurement report message may be employed to transmit measurementresults.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g. a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 stored in non-transitory memory 315 and executable bythe at least one processor 314. The wireless device 110 may furthercomprise at least one of at least one speaker/microphone 311, at leastone keypad 312, at least one display/touchpad 313, at least one powersource 317, at least one global positioning system (GPS) chipset 318,and other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding/processing, data processing, powercontrol, input/output processing, and/or any other functionality thatmay enable the wireless device 110, the base station 1 120A and/or thebase station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to thespeaker/microphone 311, the keypad 312, and/or the display/touchpad 313.The processor 314 may receive user input data from and/or provide useroutput data to the speaker/microphone 311, the keypad 312, and/or thedisplay/touchpad 313. The processor 314 in the wireless device 110 mayreceive power from the power source 317 and/or may be configured todistribute the power to the other components in the wireless device 110.The power source 317 may comprise at least one of one or more dry cellbatteries, solar cells, fuel cells, and the like. The processor 314 maybe connected to the GPS chipset 318. The GPS chipset 318 may beconfigured to provide geographic location information of the wirelessdevice 110.

The processor 314 of the wireless device 110 may further be connected toother peripherals 319, which may comprise one or more software and/orhardware modules that provide additional features and/orfunctionalities. For example, the peripherals 319 may comprise at leastone of an accelerometer, a satellite transceiver, a digital camera, auniversal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, and thelike.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110 via a wireless link 330A and/or a wireless link 330Brespectively. In an example, the communication interface 320A of thebase station 1, 120A, may communicate with the communication interface320B of the base station 2 and other RAN and core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110 and/or thebase station 2 120B and the wireless device 110 may be configured tosend and receive transport blocks via the wireless link 330A and/or viathe wireless link 330B, respectively. The wireless link 330A and/or thewireless link 330B may employ at least one frequency carrier. Accordingto some of various aspects of embodiments, transceiver(s) may beemployed. A transceiver may be a device that comprises both atransmitter and a receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in thecommunication interface 310, 320A, 320B and the wireless link 330A, 330Bare illustrated in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A,FIG. 7B, FIG. 8, and associated text.

In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF,etc) may comprise one or more communication interfaces, one or moreprocessors, and memory storing instructions.

A node (e.g. wireless device, base station, AMF, SMF, UPF, servers,switches, antennas, and/or the like) may comprise one or moreprocessors, and memory storing instructions that when executed by theone or more processors causes the node to perform certain processesand/or functions. Example embodiments may enable operation ofsingle-carrier and/or multi-carrier communications. Other exampleembodiments may comprise a non-transitory tangible computer readablemedia comprising instructions executable by one or more processors tocause operation of single-carrier and/or multi-carrier communications.Yet other example embodiments may comprise an article of manufacturethat comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a node to enable operation ofsingle-carrier and/or multi-carrier communications. The node may includeprocessors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and code stored in and/or incommunication with a memory device to implement connections, electronicdevice operations, protocol(s), protocol layers, communication drivers,device drivers, hardware operations, combinations thereof, and/or thelike.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 4A shows an example uplink transmitter forat least one physical channel. A baseband signal representing a physicaluplink shared channel may perform one or more functions. The one or morefunctions may comprise at least one of: scrambling; modulation ofscrambled bits to generate complex-valued symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; transform precoding to generate complex-valued symbols;precoding of the complex-valued symbols; mapping of precodedcomplex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 4A. These functions are illustrated as examples andit is anticipated that other mechanisms may be implemented in variousembodiments.

An example structure for modulation and up-conversion to the carrierfrequency of the complex-valued SC-FDMA or CP-OFDM baseband signal foran antenna port and/or the complex-valued Physical Random Access CHannel(PRACH) baseband signal is shown in FIG. 4B. Filtering may be employedprior to transmission.

An example structure for downlink transmissions is shown in FIG. 4C. Thebaseband signal representing a downlink physical channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

In an example, a gNB may transmit a first symbol and a second symbol onan antenna port, to a wireless device. The wireless device may infer thechannel (e.g., fading gain, multipath delay, etc.) for conveying thesecond symbol on the antenna port, from the channel for conveying thefirst symbol on the antenna port. In an example, a first antenna portand a second antenna port may be quasi co-located if one or morelarge-scale properties of the channel over which a first symbol on thefirst antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;doppler spread; doppler shift; average gain; average delay; and/orspatial Receiving (Rx) parameters.

An example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.4D. Filtering may be employed prior to transmission.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals. FIG. 5B is a diagram of an example downlinkchannel mapping and a downlink physical signals. In an example, aphysical layer may provide one or more information transfer services toa MAC and/or one or more higher layers. For example, the physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and with what characteristics data are transferred over theradio interface.

In an example embodiment, a radio network may comprise one or moredownlink and/or uplink transport channels. For example, a diagram inFIG. 5A shows example uplink transport channels comprising Uplink-SharedCHannel (UL-SCH) 501 and Random Access CHannel (RACH) 502. A diagram inFIG. 5B shows example downlink transport channels comprisingDownlink-Shared CHannel (DL-SCH) 511, Paging CHannel (PCH) 512, andBroadcast CHannel (BCH) 513. A transport channel may be mapped to one ormore corresponding physical channels. For example, UL-SCH 501 may bemapped to Physical Uplink Shared CHannel (PUSCH) 503. RACH 502 may bemapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to PhysicalDownlink Shared CHannel (PDSCH) 514. BCH 513 may be mapped to PhysicalBroadcast CHannel (PBCH) 516.

There may be one or more physical channels without a correspondingtransport channel. The one or more physical channels may be employed forUplink Control Information (UCI) 509 and/or Downlink Control Information(DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 maycarry UCI 509 from a UE to a base station. For example, PhysicalDownlink Control CHannel (PDCCH) 515 may carry DCI 517 from a basestation to a UE. NR may support UCI 509 multiplexing in PUSCH 503 whenUCI 509 and PUSCH 503 transmissions may coincide in a slot at least inpart. The UCI 509 may comprise at least one of CSI, Acknowledgement(ACK)/Negative Acknowledgement (NACK), and/or scheduling request. TheDCI 517 on PDCCH 515 may indicate at least one of following: one or moredownlink assignments and/or one or more uplink scheduling grants

In uplink, a UE may transmit one or more Reference Signals (RSs) to abase station. For example, the one or more RSs may be at least one ofDemodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and/orSounding RS (SRS) 508. In downlink, a base station may transmit (e.g.,unicast, multicast, and/or broadcast) one or more RSs to a UE. Forexample, the one or more RSs may be at least one of PrimarySynchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521,CSI-RS 522, DM-RS 523, and/or PT-RS 524.

In an example, a UE may transmit one or more uplink DM-RSs 506 to a basestation for channel estimation, for example, for coherent demodulationof one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH504). For example, a UE may transmit a base station at least one uplinkDM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least oneuplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. In an example, a base station mayconfigure a UE with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to transmit at one or more symbols of a PUSCH and/or PUCCH. Abase station may semi-statistically configure a UE with a maximum numberof front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UEmay schedule a single-symbol DM-RS and/or double symbol DM-RS based on amaximum number of front-loaded DM-RS symbols, wherein a base station mayconfigure the UE with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, e.g., at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

In an example, whether uplink PT-RS 507 is present or not may depend ona RRC configuration. For example, a presence of uplink PT-RS may beUE-specifically configured. For example, a presence and/or a pattern ofuplink PT-RS 507 in a scheduled resource may be UE-specificallyconfigured by a combination of RRC signaling and/or association with oneor more parameters employed for other purposes (e.g., Modulation andCoding Scheme (MCS)) which may be indicated by DCI. When configured, adynamic presence of uplink PT-RS 507 may be associated with one or moreDCI parameters comprising at least MCS. A radio network may supportplurality of uplink PT-RS densities defined in time/frequency domain.When present, a frequency domain density may be associated with at leastone configuration of a scheduled bandwidth. A UE may assume a sameprecoding for a DMRS port and a PT-RS port. A number of PT-RS ports maybe fewer than a number of DM-RS ports in a scheduled resource. Forexample, uplink PT-RS 507 may be confined in the scheduledtime/frequency duration for a UE.

In an example, a UE may transmit SRS 508 to a base station for channelstate estimation to support uplink channel dependent scheduling and/orlink adaptation. For example, SRS 508 transmitted by a UE may allow fora base station to estimate an uplink channel state at one or moredifferent frequencies. A base station scheduler may employ an uplinkchannel state to assign one or more resource blocks of good quality foran uplink PUSCH transmission from a UE. A base station maysemi-statistically configure a UE with one or more SRS resource sets.For an SRS resource set, a base station may configure a UE with one ormore SRS resources. An SRS resource set applicability may be configuredby a higher layer (e.g., RRC) parameter. For example, when a higherlayer parameter indicates beam management, a SRS resource in each of oneor more SRS resource sets may be transmitted at a time instant. A UE maytransmit one or more SRS resources in different SRS resource setssimultaneously. A new radio network may support aperiodic, periodicand/or semi-persistent SRS transmissions. A UE may transmit SRSresources based on one or more trigger types, wherein the one or moretrigger types may comprise higher layer signaling (e.g., RRC) and/or oneor more DCI formats (e.g., at least one DCI format may be employed for aUE to select at least one of one or more configured SRS resource sets.An SRS trigger type 0 may refer to an SRS triggered based on a higherlayer signaling. An SRS trigger type 1 may refer to an SRS triggeredbased on one or more DCI formats. In an example, when PUSCH 503 and SRS508 are transmitted in a same slot, a UE may be configured to transmitSRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS506.

In an example, a base station may semi-statistically configure a UE withone or more SRS configuration parameters indicating at least one offollowing: a SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, afrequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.

In an example, in a time domain, an SS/PBCH block may comprise one ormore OFDM symbols (e.g., 4 OFDM symbols numbered in increasing orderfrom 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprisePSS/SSS 521 and PBCH 516. In an example, in the frequency domain, anSS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240contiguous subcarriers with the subcarriers numbered in increasing orderfrom 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 mayoccupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may spanacross 3 OFDM symbols and 240 subcarriers. A UE may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, e.g., with respect to Doppler spread, Doppler shift, averagegain, average delay, and spatial Rx parameters. A UE may not assumequasi co-location for other SS/PBCH block transmissions. A periodicityof an SS/PBCH block may be configured by a radio network (e.g., by anRRC signaling) and one or more time locations where the SS/PBCH blockmay be sent may be determined by sub-carrier spacing. In an example, aUE may assume a band-specific sub-carrier spacing for an SS/PBCH blockunless a radio network has configured a UE to assume a differentsub-carrier spacing.

In an example, downlink CSI-RS 522 may be employed for a UE to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522.For example, a base station may semi-statistically configure and/orreconfigure a UE with periodic transmission of downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated ad/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation ofCSI-RS resource may be triggered dynamically. In an example, CSI-RSconfiguration may comprise one or more parameters indicating at least anumber of antenna ports. For example, a base station may configure a UEwith 32 ports. A base station may semi-statistically configure a UE withone or more CSI-RS resource sets. One or more CSI-RS resources may beallocated from one or more CSI-RS resource sets to one or more UEs. Forexample, a base station may semi-statistically configure one or moreparameters indicating CSI RS resource mapping, for example, time-domainlocation of one or more CSI-RS resources, a bandwidth of a CSI-RSresource, and/or a periodicity. In an example, a UE may be configured toemploy a same OFDM symbols for downlink CSI-RS 522 and control resourceset (coreset) when the downlink CSI-RS 522 and coreset are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are the outside of PRBs configured for coreset. In anexample, a UE may be configured to employ a same OFDM symbols fordownlink CSI-RS 522 and SS/PBCH blocks when the downlink CSI-RS 522 andSS/PBCH blocks are spatially quasi co-located and resource elementsassociated with the downlink CSI-RS 522 are the outside of PRBsconfigured for SS/PBCH blocks.

In an example, a UE may transmit one or more downlink DM-RSs 523 to abase station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). For example, a radio network may support one or more variableand/or configurable DM-RS patterns for data demodulation. At least onedownlink DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-statisticallyconfigure a UE with a maximum number of front-loaded DM-RS symbols forPDSCH 514. For example, a DM-RS configuration may support one or moreDM-RS ports. For example, for single user-MIMO, a DM-RS configurationmay support at least 8 orthogonal downlink DM-RS ports. For example, formultiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlinkDM-RS ports. A radio network may support, e.g., at least for CP-OFDM, acommon DM-RS structure for DL and UL, wherein a DM-RS location, DM-RSpattern, and/or scrambling sequence may be same or different.

In an example, whether downlink PT-RS 524 is present or not may dependon a RRC configuration. For example, a presence of downlink PT-RS 524may be UE-specifically configured. For example, a presence and/or apattern of downlink PT-RS 524 in a scheduled resource may beUE-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters employed for other purposes(e.g., MCS) which may be indicated by DCI. When configured, a dynamicpresence of downlink PT-RS 524 may be associated with one or more DCIparameters comprising at least MCS. A radio network may supportplurality of PT-RS densities defined in time/frequency domain. Whenpresent, a frequency domain density may be associated with at least oneconfiguration of a scheduled bandwidth. A UE may assume a same precodingfor a DMRS port and a PT-RS port. A number of PT-RS ports may be fewerthan a number of DM-RS ports in a scheduled resource. For example,downlink PT-RS 524 may be confined in the scheduled time/frequencyduration for a UE.

FIG. 6 is a diagram depicting an example transmission time and receptiontime for a carrier as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers, in case ofcarrier aggregation, or ranging from 1 to 64 carriers, in case of dualconnectivity. Different radio frame structures may be supported (e.g.,for FDD and for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. In this example, radio frame duration is 10 ms. In thisexample, a 10 ms radio frame 601 may be divided into ten equally sizedsubframes 602 with 1 ms duration. Subframe(s) may comprise one or moreslots (e.g. slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. Slot(s) may include a plurality of OFDM symbols 604.The number of OFDM symbols 604 in a slot 605 may depend on the cyclicprefix length. For example, a slot may be 14 OFDM symbols for the samesubcarrier spacing of up to 480 kHz with normal CP. A slot may be 12OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP.A slot may contain downlink, uplink, or a downlink part and an uplinkpart and/or alike.

FIG. 7A is a diagram depicting example sets of OFDM subcarriers as peran aspect of an embodiment of the present disclosure. In the example, agNB may communicate with a wireless device with a carrier with anexample channel bandwidth 700. Arrow(s) in the diagram may depict asubcarrier in a multicarrier OFDM system. The OFDM system may usetechnology such as OFDM technology, SC-FDMA technology, and/or the like.In an example, an arrow 701 shows a subcarrier transmitting informationsymbols. In an example, a subcarrier spacing 702, between two contiguoussubcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120KHz, 240 KHz etc. In an example, different subcarrier spacing maycorrespond to different transmission numerologies. In an example, atransmission numerology may comprise at least: a numerology index; avalue of subcarrier spacing; a type of cyclic prefix (CP). In anexample, a gNB may transmit to/receive from a UE on a number ofsubcarriers 703 in a carrier. In an example, a bandwidth occupied by anumber of subcarriers 703 (transmission bandwidth) may be smaller thanthe channel bandwidth 700 of a carrier, due to guard band 704 and 705.In an example, a guard band 704 and 705 may be used to reduceinterference to and from one or more neighbor carriers. A number ofsubcarriers (transmission bandwidth) in a carrier may depend on thechannel bandwidth of the carrier and the subcarrier spacing. Forexample, a transmission bandwidth, for a carrier with 20 MHz channelbandwidth and 15 KHz subcarrier spacing, may be in number of 1024subcarriers.

In an example, a gNB and a wireless device may communicate with multipleCCs when configured with CA. In an example, different component carriersmay have different bandwidth and/or subcarrier spacing, if CA issupported. In an example, a gNB may transmit a first type of service toa UE on a first component carrier. The gNB may transmit a second type ofservice to the UE on a second component carrier. Different type ofservices may have different service requirement (e.g., data rate,latency, reliability), which may be suitable for transmission viadifferent component carrier having different subcarrier spacing and/orbandwidth. FIG. 7B shows an example embodiment. A first componentcarrier may comprise a first number of subcarriers 706 with a firstsubcarrier spacing 709. A second component carrier may comprise a secondnumber of subcarriers 707 with a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 with athird subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. In an example, a carrier mayhave a transmission bandwidth 801. In an example, a resource grid may bein a structure of frequency domain 802 and time domain 803. In anexample, a resource grid may comprise a first number of OFDM symbols ina subframe and a second number of resource blocks, starting from acommon resource block indicated by higher-layer signaling (e.g. RRCsignaling), for a transmission numerology and a carrier. In an example,in a resource grid, a resource unit identified by a subcarrier index anda symbol index may be a resource element 805. In an example, a subframemay comprise a first number of OFDM symbols 807 depending on anumerology associated with a carrier. For example, when a subcarrierspacing of a numerology of a carrier is 15 KHz, a subframe may have 14OFDM symbols for a carrier. When a subcarrier spacing of a numerology is30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacingof a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. Inan example, a second number of resource blocks comprised in a resourcegrid of a carrier may depend on a bandwidth and a numerology of thecarrier.

As shown in FIG. 8, a resource block 806 may comprise 12 subcarriers. Inan example, multiple resource blocks may be grouped into a ResourceBlock Group (RBG) 804. In an example, a size of a RBG may depend on atleast one of: a RRC message indicating a RBG size configuration; a sizeof a carrier bandwidth; or a size of a bandwidth part of a carrier. Inan example, a carrier may comprise multiple bandwidth parts. A firstbandwidth part of a carrier may have different frequency location and/orbandwidth from a second bandwidth part of the carrier.

In an example, a gNB may transmit a downlink control informationcomprising a downlink or uplink resource block assignment to a wirelessdevice. A base station may transmit to or receive from, a wirelessdevice, data packets (e.g. transport blocks) scheduled and transmittedvia one or more resource blocks and one or more slots according toparameters in a downlink control information and/or RRC message(s). Inan example, a starting symbol relative to a first slot of the one ormore slots may be indicated to the wireless device. In an example, a gNBmay transmit to or receive from, a wireless device, data packetsscheduled on one or more RBGs and one or more slots.

In an example, a gNB may transmit a downlink control informationcomprising a downlink assignment to a wireless device via one or morePDCCHs. The downlink assignment may comprise parameters indicating atleast modulation and coding format; resource allocation; and/or HARQinformation related to DL-SCH. In an example, a resource allocation maycomprise parameters of resource block allocation; and/or slotallocation. In an example, a gNB may dynamically allocate resources to awireless device via a Cell-Radio Network Temporary Identifier (C-RNTI)on one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible allocation when its downlink receptionis enabled. The wireless device may receive one or more downlink datapackage on one or more PDSCH scheduled by the one or more PDCCHs, whensuccessfully detecting the one or more PDCCHs.

In an example, a gNB may allocate Configured Scheduling (CS) resourcesfor down link transmission to a wireless device. The gNB may transmitone or more RRC messages indicating a periodicity of the CS grant. ThegNB may transmit a DCI via a PDCCH addressed to a ConfiguredScheduling-RNTI (CS-RNTI) activating the CS resources. The DCI maycomprise parameters indicating that the downlink grant is a CS grant.The CS grant may be implicitly reused according to the periodicitydefined by the one or more RRC messages, until deactivated.

In an example, a gNB may transmit a downlink control informationcomprising an uplink grant to a wireless device via one or more PDCCHs.The uplink grant may comprise parameters indicating at least modulationand coding format; resource allocation; and/or HARQ information relatedto UL-SCH. In an example, a resource allocation may comprise parametersof resource block allocation; and/or slot allocation. In an example, agNB may dynamically allocate resources to a wireless device via a C-RNTIon one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible resource allocation. The wirelessdevice may transmit one or more uplink data package via one or morePUSCH scheduled by the one or more PDCCHs, when successfully detectingthe one or more PDCCHs.

In an example, a gNB may allocate CS resources for uplink datatransmission to a wireless device. The gNB may transmit one or more RRCmessages indicating a periodicity of the CS grant. The gNB may transmita DCI via a PDCCH addressed to a CS-RNTI activating the CS resources.The DCI may comprise parameters indicating that the uplink grant is a CSgrant. The CS grant may be implicitly reused according to theperiodicity defined by the one or more RRC message, until deactivated.

In an example, a base station may transmit DCI/control signaling viaPDCCH. The DCI may take a format in a plurality of formats. A DCI maycomprise downlink and/or uplink scheduling information (e.g., resourceallocation information, HARQ related parameters, MCS), request for CSI(e.g., aperiodic CQI reports), request for SRS, uplink power controlcommands for one or more cells, one or more timing information (e.g., TBtransmission/reception timing, HARQ feedback timing, etc.), etc. In anexample, a DCI may indicate an uplink grant comprising transmissionparameters for one or more transport blocks. In an example, a DCI mayindicate downlink assignment indicating parameters for receiving one ormore transport blocks. In an example, a DCI may be used by base stationto initiate a contention-free random access at the wireless device. Inan example, the base station may transmit a DCI comprising slot formatindicator (SFI) notifying a slot format. In an example, the base stationmay transmit a DCI comprising pre-emption indication notifying thePRB(s) and/or OFDM symbol(s) where a UE may assume no transmission isintended for the UE. In an example, the base station may transmit a DCIfor group power control of PUCCH or PUSCH or SRS. In an example, a DCImay correspond to an RNTI. In an example, the wireless device may obtainan RNTI in response to completing the initial access (e.g., C-RNTI). Inan example, the base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI(e.g., the wireless device may compute RA-RNTI based on resources usedfor transmission of a preamble). In an example, an RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). In an example, awireless device may monitor a group common search space which may beused by base station for transmitting DCIs that are intended for a groupof UEs. In an example, a group common DCI may correspond to an RNTIwhich is commonly configured for a group of UEs. In an example, awireless device may monitor a UE-specific search space. In an example, aUE specific DCI may correspond to an RNTI configured for the wirelessdevice.

A NR system may support a single beam operation and/or a multi-beamoperation. In a multi-beam operation, a base station may perform adownlink beam sweeping to provide coverage for common control channelsand/or downlink SS blocks, which may comprise at least a PSS, a SSS,and/or PBCH. A wireless device may measure quality of a beam pair linkusing one or more RSs. One or more SS blocks, or one or more CSI-RSresources, associated with a CSI-RS resource index (CRI), or one or moreDM-RSs of PBCH, may be used as RS for measuring quality of a beam pairlink. Quality of a beam pair link may be defined as a reference signalreceived power (RSRP) value, or a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. A RS resource and DM-RSs of a control channel may be calledQCLed when a channel characteristics from a transmission on an RS to awireless device, and that from a transmission on a control channel to awireless device, are similar or same under a configured criterion. In amulti-beam operation, a wireless device may perform an uplink beamsweeping to access a cell.

In an example, a wireless device may be configured to monitor PDCCH onone or more beam pair links simultaneously depending on a capability ofa wireless device. This may increase robustness against beam pair linkblocking. A base station may transmit one or more messages to configurea wireless device to monitor PDCCH on one or more beam pair links indifferent PDCCH OFDM symbols. For example, a base station may transmithigher layer signaling (e.g. RRC signaling) or MAC CE comprisingparameters related to the Rx beam setting of a wireless device formonitoring PDCCH on one or more beam pair links. A base station maytransmit indication of spatial QCL assumption between an DL RS antennaport(s) (for example, cell-specific CSI-RS, or wireless device-specificCSI-RS, or SS block, or PBCH with or without DM-RSs of PBCH), and DL RSantenna port(s) for demodulation of DL control channel. Signaling forbeam indication for a PDCCH may be MAC CE signaling, or RRC signaling,or DCI signaling, or specification-transparent and/or implicit method,and combination of these signaling methods.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. The base station may transmit DCI (e.g.downlink grants) comprising information indicating the RS antennaport(s). The information may indicate RS antenna port(s) which may beQCLed with the DM-RS antenna port(s). Different set of DM-RS antennaport(s) for a DL data channel may be indicated as QCL with different setof the RS antenna port(s).

FIG. 9A is an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. For example, in a multi-beamoperation, a base station 120 may transmit SS blocks in multiple beams,together forming a SS burst 940. One or more SS blocks may betransmitted on one beam. If multiple SS bursts 940 are transmitted withmultiple beams, SS bursts together may form SS burst set 950.

A wireless device may further use CSI-RS in the multi-beam operation forestimating a beam quality of a links between a wireless device and abase station. A beam may be associated with a CSI-RS. For example, awireless device may, based on a RSRP measurement on CSI-RS, report abeam index, as indicated in a CRI for downlink beam selection, andassociated with a RSRP value of a beam. A CSI-RS may be transmitted on aCSI-RS resource including at least one of one or more antenna ports, oneor more time or frequency radio resources. A CSI-RS resource may beconfigured in a cell-specific way by common RRC signaling, or in awireless device-specific way by dedicated RRC signaling, and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be transmitted periodically, or using aperiodictransmission, or using a multi-shot or semi-persistent transmission. Forexample, in a periodic transmission in FIG. 9A, a base station 120 maytransmit configured CSI-RS resources 940 periodically using a configuredperiodicity in a time domain. In an aperiodic transmission, a configuredCSI-RS resource may be transmitted in a dedicated time slot. In amulti-shot or semi-persistent transmission, a configured CSI-RS resourcemay be transmitted within a configured period. Beams used for CSI-RStransmission may have different beam width than beams used for SS-blockstransmission.

FIG. 9B is an example of a beam management procedure in an example newradio network. A base station 120 and/or a wireless device 110 mayperform a downlink L1/L2 beam management procedure. One or more of thefollowing downlink L1/L2 beam management procedures may be performedwithin one or more wireless devices 110 and one or more base stations120. In an example, a P-1 procedure 910 may be used to enable thewireless device 110 to measure one or more Transmission (Tx) beamsassociated with the base station 120 to support a selection of a firstset of Tx beams associated with the base station 120 and a first set ofRx beam(s) associated with a wireless device 110. For beamforming at abase station 120, a base station 120 may sweep a set of different TXbeams. For beamforming at a wireless device 110, a wireless device 110may sweep a set of different Rx beams. In an example, a P-2 procedure920 may be used to enable a wireless device 110 to measure one or moreTx beams associated with a base station 120 to possibly change a firstset of Tx beams associated with a base station 120. A P-2 procedure 920may be performed on a possibly smaller set of beams for beam refinementthan in the P-1 procedure 910. A P-2 procedure 920 may be a special caseof a P-1 procedure 910. In an example, a P-3 procedure 930 may be usedto enable a wireless device 110 to measure at least one Tx beamassociated with a base station 120 to change a first set of Rx beamsassociated with a wireless device 110.

A wireless device 110 may transmit one or more beam management reportsto a base station 120. In one or more beam management reports, awireless device 110 may indicate some beam pair quality parameters,comprising at least, one or more beam identifications; RSRP; PrecodingMatrix Indicator (PMI)/Channel Quality Indicator (CQI)/Rank Indicator(RI) of a subset of configured beams. Based on one or more beammanagement reports, a base station 120 may transmit to a wireless device110 a signal indicating that one or more beam pair links are one or moreserving beams. A base station 120 may transmit PDCCH and PDSCH for awireless device 110 using one or more serving beams.

In an example embodiment, new radio network may support a BandwidthAdaptation (BA). In an example, receive and/or transmit bandwidthsconfigured by an UE employing a BA may not be large. For example, areceive and/or transmit bandwidths may not be as large as a bandwidth ofa cell. Receive and/or transmit bandwidths may be adjustable. Forexample, a UE may change receive and/or transmit bandwidths, e.g., toshrink during period of low activity to save power. For example, a UEmay change a location of receive and/or transmit bandwidths in afrequency domain, e.g. to increase scheduling flexibility. For example,a UE may change a subcarrier spacing, e.g. to allow different services.

In an example embodiment, a subset of a total cell bandwidth of a cellmay be referred to as a Bandwidth Part (BWP). A base station mayconfigure a UE with one or more BWPs to achieve a BA. For example, abase station may indicate, to a UE, which of the one or more(configured) BWPs is an active BWP.

FIG. 10 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050)with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030with a width of 20 MHz and subcarrier spacing of 60 kHz.

In an example, a UE, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g. RRC layer)for a cell a set of one or more BWPs (e.g., at most four BWPs) forreceptions by the UE (DL BWP set) in a DL bandwidth by at least oneparameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs)for transmissions by a UE (UL BWP set) in an UL bandwidth by at leastone parameter UL-BWP for a cell.

To enable BA on the PCell, a base station may configure a UE with one ormore UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA),a base station may configure a UE at least with one or more DL BWPs(e.g., there may be none in an UL).

In an example, an initial active DL BWP may be defined by at least oneof a location and number of contiguous PRBs, a subcarrier spacing, or acyclic prefix, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a UE is configured with a secondary carrier on a primary cell, the UEmay be configured with an initial BWP for random access procedure on asecondary carrier.

In an example, for unpaired spectrum operation, a UE may expect that acenter frequency for a DL BWP may be same as a center frequency for a ULBWP.

For example, for a DL BWP or an UL BWP in a set of one or more DL BWPsor one or more UL BWPs, respectively, a base station maysemi-statistically configure a UE for a cell with one or more parametersindicating at least one of following: a subcarrier spacing; a cyclicprefix; a number of contiguous PRBs; an index in the set of one or moreDL BWPs and/or one or more UL BWPs; a link between a DL BWP and an ULBWP from a set of configured DL BWPs and UL BWPs; a DCI detection to aPDSCH reception timing; a PDSCH reception to a HARQ-ACK transmissiontiming value; a DCI detection to a PUSCH transmission timing value; anoffset of a first PRB of a DL bandwidth or an UL bandwidth,respectively, relative to a first PRB of a bandwidth.

In an example, for a DL BWP in a set of one or more DL BWPs on a PCell,a base station may configure a UE with one or more control resource setsfor at least one type of common search space and/or one UE-specificsearch space. For example, a base station may not configure a UE withouta common search space on a PCell, or on a PSCell, in an active DL BWP.

For an UL BWP in a set of one or more UL BWPs, a base station mayconfigure a UE with one or more resource sets for one or more PUCCHtransmissions.

In an example, if a DCI comprises a BWP indicator field, a BWP indicatorfield value may indicate an active DL BWP, from a configured DL BWP set,for one or more DL receptions. If a DCI comprises a BWP indicator field,a BWP indicator field value may indicate an active UL BWP, from aconfigured UL BWP set, for one or more UL transmissions.

In an example, for a PCell, a base station may semi-statisticallyconfigure a UE with a default DL BWP among configured DL BWPs. If a UEis not provided a default DL BWP, a default BWP may be an initial activeDL BWP.

In an example, a base station may configure a UE with a timer value fora PCell. For example, a UE may start a timer, referred to as BWPinactivity timer, when a UE detects a DCI indicating an active DL BWP,other than a default DL BWP, for a paired spectrum operation or when aUE detects a DCI indicating an active DL BWP or UL BWP, other than adefault DL BWP or UL BWP, for an unpaired spectrum operation. The UE mayincrement the timer by an interval of a first value (e.g., the firstvalue may be 1 millisecond or 0.5 milliseconds) if the UE does notdetect a DCI during the interval for a paired spectrum operation or foran unpaired spectrum operation. In an example, the timer may expire whenthe timer is equal to the timer value. A UE may switch to the default DLBWP from an active DL BWP when the timer expires.

In an example, a base station may semi-statistically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of BWP inactivity timer(for example, the second BWP may be a default BWP). For example, FIG. 10is an example diagram of 3 BWPs configured, BWP1 (1010 and 1050), BWP2(1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a defaultBWP. BWP1 (1010) may be an initial active BWP. In an example, a UE mayswitch an active BWP from BWP1 1010 to BWP2 1020 in response to anexpiry of BWP inactivity timer. For example, a UE may switch an activeBWP from BWP2 1020 to BWP3 1030 in response to receiving a DCIindicating BWP3 1030 as an active BWP. Switching an active BWP from BWP31030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be in responseto receiving a DCI indicating an active BWP and/or in response to anexpiry of BWP inactivity timer.

In an example, if a UE is configured for a secondary cell with a defaultDL BWP among configured DL BWPs and a timer value, UE procedures on asecondary cell may be same as on a primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a base station configures a UE with a first active DLBWP and a first active UL BWP on a secondary cell or carrier, a UE mayemploy an indicated DL BWP and an indicated UL BWP on a secondary cellas a respective first active DL BWP and first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows employing a multi connectivity(e.g. dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A is an example diagram of a protocol structure of awireless device 110 (e.g. UE) with CA and/or multi connectivity as peran aspect of an embodiment. FIG. 11B is an example diagram of a protocolstructure of multiple base stations with CA and/or multi connectivity asper an aspect of an embodiment. The multiple base stations may comprisea master node, MN 1130 (e.g. a master node, a master base station, amaster gNB, a master eNB, and/or the like) and a secondary node, SN 1150(e.g. a secondary node, a secondary base station, a secondary gNB, asecondary eNB, and/or the like). A master node 1130 and a secondary node1150 may co-work to communicate with a wireless device 110.

When multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception/transmissionfunctions in an RRC connected state, may be configured to utilize radioresources provided by multiple schedulers of a multiple base stations.Multiple base stations may be inter-connected via a non-ideal or idealbackhaul (e.g. Xn interface, X2 interface, and/or the like). A basestation involved in multi connectivity for a certain wireless device mayperform at least one of two different roles: a base station may eitheract as a master base station or as a secondary base station. In multiconnectivity, a wireless device may be connected to one master basestation and one or more secondary base stations. In an example, a masterbase station (e.g. the MN 1130) may provide a master cell group (MCG)comprising a primary cell and/or one or more secondary cells for awireless device (e.g. the wireless device 110). A secondary base station(e.g. the SN 1150) may provide a secondary cell group (SCG) comprising aprimary secondary cell (PSCell) and/or one or more secondary cells for awireless device (e.g. the wireless device 110).

In multi connectivity, a radio protocol architecture that a beareremploys may depend on how a bearer is setup. In an example, threedifferent type of bearer setup options may be supported: an MCG bearer,an SCG bearer, and/or a split bearer. A wireless device mayreceive/transmit packets of an MCG bearer via one or more cells of theMCG, and/or may receive/transmits packets of an SCG bearer via one ormore cells of an SCG. Multi-connectivity may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not beconfigured/implemented in some of the example embodiments.

In an example, a wireless device (e.g. Wireless Device 110) may transmitand/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP 1111), an RLC layer (e.g. MN RLC1114), and a MAC layer (e.g. MN MAC 1118); packets of a split bearer viaan SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1112), one ofa master or secondary RLC layer (e.g. MN RLC 1115, SN RLC 1116), and oneof a master or secondary MAC layer (e.g. MN MAC 1118, SN MAC 1119);and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP 1110), aPDCP layer (e.g. NR PDCP 1113), an RLC layer (e.g. SN RLC 1117), and aMAC layer (e.g. MN MAC 1119).

In an example, a master base station (e.g. MN 1130) and/or a secondarybase station (e.g. SN 1150) may transmit/receive: packets of an MCGbearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP 1121, NR PDCP1142), a master node RLC layer (e.g. MN RLC 1124, MN RLC 1125), and amaster node MAC layer (e.g. MN MAC 1128); packets of an SCG bearer via amaster or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1122, NR PDCP 1143), asecondary node RLC layer (e.g. SN RLC 1146, SN RLC 1147), and asecondary node MAC layer (e.g. SN MAC 1148); packets of a split bearervia a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1123, NR PDCP 1141), amaster or secondary node RLC layer (e.g. MN RLC 1126, SN RLC 1144, SNRLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g.MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities: one MAC entity (e.g. MN MAC 1118) for a master base station,and other MAC entities (e.g. SN MAC 1119) for a secondary base station.In multi-connectivity, a configured set of serving cells for a wirelessdevice may comprise two subsets: an MCG comprising serving cells of amaster base station, and SCGs comprising serving cells of a secondarybase station. For an SCG, one or more of following configurations may beapplied: at least one cell of an SCG has a configured UL CC and at leastone cell of a SCG, named as primary secondary cell (PSCell, PCell ofSCG, or sometimes called PCell), is configured with PUCCH resources;when an SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or a number of NR RLC retransmissions hasbeen reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, forsplit bearer, a DL data transfer over a master base station may bemaintained; an NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer; PCell and/or PSCell may not be de-activated; PSCellmay be changed with a SCG change procedure (e.g. with security keychange and a RACH procedure); and/or a bearer type change between asplit bearer and a SCG bearer or simultaneous configuration of a SCG anda split bearer may or may not supported.

With respect to interaction between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be applied: a master base station and/or a secondary basestation may maintain Radio Resource Management (RRM) measurementconfigurations of a wireless device; a master base station may (e.g.based on received measurement reports, traffic conditions, and/or bearertypes) may decide to request a secondary base station to provideadditional resources (e.g. serving cells) for a wireless device; uponreceiving a request from a master base station, a secondary base stationmay create/modify a container that may result in configuration ofadditional serving cells for a wireless device (or decide that thesecondary base station has no resource available to do so); for a UEcapability coordination, a master base station may provide (a part of)an AS configuration and UE capabilities to a secondary base station; amaster base station and a secondary base station may exchangeinformation about a UE configuration by employing of RRC containers(inter-node messages) carried via Xn messages; a secondary base stationmay initiate a reconfiguration of the secondary base station existingserving cells (e.g. PUCCH towards the secondary base station); asecondary base station may decide which cell is a PSCell within a SCG; amaster base station may or may not change content of RRC configurationsprovided by a secondary base station; in case of a SCG addition and/or aSCG SCell addition, a master base station may provide recent (or thelatest) measurement results for SCG cell(s); a master base station andsecondary base stations may receive information of SFN and/or subframeoffset of each other from OAM and/or via an Xn interface, (e.g. for apurpose of DRX alignment and/or identification of a measurement gap). Inan example, when adding a new SCG SCell, dedicated RRC signaling may beused for sending required system information of a cell as for CA, exceptfor a SFN acquired from a MIB of a PSCell of a SCG.

FIG. 12 is an example diagram of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival during RRC_CONNECTED when UL synchronization status isnon-synchronized, transition from RRC_Inactive, and/or request for othersystem information. For example, a PDCCH order, a MAC entity, and/or abeam failure indication may initiate a random access procedure.

In an example embodiment, a random access procedure may be at least oneof a contention based random access procedure and a contention freerandom access procedure. For example, a contention based random accessprocedure may comprise, one or more Msg 1 1220 transmissions, one ormore Msg2 1230 transmissions, one or more Msg3 1240 transmissions, andcontention resolution 1250. For example, a contention free random accessprocedure may comprise one or more Msg 1 1220 transmissions and one ormore Msg2 1230 transmissions.

In an example, a base station may transmit (e.g., unicast, multicast, orbroadcast), to a UE, a RACH configuration 1210 via one or more beams.The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: available set of PRACH resourcesfor a transmission of a random access preamble, initial preamble power(e.g., random access preamble initial received target power), an RSRPthreshold for a selection of a SS block and corresponding PRACHresource, a power-ramping factor (e.g., random access preamble powerramping step), random access preamble index, a maximum number ofpreamble transmission, preamble group A and group B, a threshold (e.g.,message size) to determine the groups of random access preambles, a setof one or more random access preambles for system information requestand corresponding PRACH resource(s), if any, a set of one or more randomaccess preambles for beam failure recovery request and correspondingPRACH resource(s), if any, a time window to monitor RA response(s), atime window to monitor response(s) on beam failure recovery request,and/or a contention resolution timer.

In an example, the Msg1 1220 may be one or more transmissions of arandom access preamble. For a contention based random access procedure,a UE may select a SS block with a RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a UE may select one or morerandom access preambles from a group A or a group B depending on apotential Msg3 1240 size. If a random access preambles group B does notexist, a UE may select the one or more random access preambles from agroup A. A UE may select a random access preamble index randomly (e.g.with equal probability or a normal distribution) from one or more randomaccess preambles associated with a selected group. If a base stationsemi-statistically configures a UE with an association between randomaccess preambles and SS blocks, the UE may select a random accesspreamble index randomly with equal probability from one or more randomaccess preambles associated with a selected SS block and a selectedgroup.

For example, a UE may initiate a contention free random access procedurebased on a beam failure indication from a lower layer. For example, abase station may semi-statistically configure a UE with one or morecontention free PRACH resources for beam failure recovery requestassociated with at least one of SS blocks and/or CSI-RSs. If at leastone of SS blocks with a RSRP above a first RSRP threshold amongstassociated SS blocks or at least one of CSI-RSs with a RSRP above asecond RSRP threshold amongst associated CSI-RSs is available, a UE mayselect a random access preamble index corresponding to a selected SSblock or CSI-RS from a set of one or more random access preambles forbeam failure recovery request.

For example, a UE may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. If a base station does not configure a UE with at least onecontention free PRACH resource associated with SS blocks or CSI-RS, theUE may select a random access preamble index. If a base stationconfigures a UE with one or more contention free PRACH resourcesassociated with SS blocks and at least one SS block with a RSRP above afirst RSRP threshold amongst associated SS blocks is available, the UEmay select the at least one SS block and select a random access preamblecorresponding to the at least one SS block. If a base station configuresa UE with one or more contention free PRACH resources associated withCSI-RSs and at least one CSI-RS with a RSRP above a second RSPRthreshold amongst the associated CSI-RSs is available, the UE may selectthe at least one CSI-RS and select a random access preamblecorresponding to the at least one CSI-RS.

A UE may perform one or more Msg1 1220 transmissions by transmitting theselected random access preamble. For example, if a UE selects an SSblock and is configured with an association between one or more PRACHoccasions and one or more SS blocks, the UE may determine an PRACHoccasion from one or more PRACH occasions corresponding to a selected SSblock. For example, if a UE selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs,the UE may determine a PRACH occasion from one or more PRACH occasionscorresponding to a selected CSI-RS. A UE may transmit, to a basestation, a selected random access preamble via a selected PRACHoccasions. A UE may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. A UE may determine a RA-RNTIassociated with a selected PRACH occasions in which a selected randomaccess preamble is transmitted. For example, a UE may not determine aRA-RNTI for a beam failure recovery request. A UE may determine anRA-RNTI at least based on an index of a first OFDM symbol and an indexof a first slot of a selected PRACH occasions, and/or an uplink carrierindex for a transmission of Msg1 1220.

In an example, a UE may receive, from a base station, a random accessresponse, Msg 2 1230. A UE may start a time window (e.g., ra-ResponseWindow) to monitor a random access response. For beam failure recoveryrequest, a base station may configure a UE with a different time window(e.g., bfr-Response Window) to monitor response on beam failure recoveryrequest. For example, a UE may start a time window (e.g.,ra-ResponseWindow or bfr-Response Window) at a start of a first PDCCHoccasion after a fixed duration of one or more symbols from an end of apreamble transmission. If a UE transmits multiple preambles, the UE maystart a time window at a start of a first PDCCH occasion after a fixedduration of one or more symbols from an end of a first preambletransmission. A UE may monitor a PDCCH of a cell for at least one randomaccess response identified by a RA-RNTI or for at least one response tobeam failure recovery request identified by a C-RNTI while a timer for atime window is running.

In an example, a UE may consider a reception of random access responsesuccessful if at least one random access response comprises a randomaccess preamble identifier corresponding to a random access preambletransmitted by the UE. A UE may consider the contention free randomaccess procedure successfully completed if a reception of random accessresponse is successful. If a contention free random access procedure istriggered for a beam failure recovery request, a UE may consider acontention free random access procedure successfully complete if a PDCCHtransmission is addressed to a C-RNTI. In an example, if at least onerandom access response comprises a random access preamble identifier, aUE may consider the random access procedure successfully completed andmay indicate a reception of an acknowledgement for a system informationrequest to upper layers. If a UE has signaled multiple preambletransmissions, the UE may stop transmitting remaining preambles (if any)in response to a successful reception of a corresponding random accessresponse.

In an example, a UE may perform one or more Msg 3 1240 transmissions inresponse to a successful reception of random access response (e.g., fora contention based random access procedure). A UE may adjust an uplinktransmission timing based on a timing advanced command indicated by arandom access response and may transmit one or more transport blocksbased on an uplink grant indicated by a random access response.Subcarrier spacing for PUSCH transmission for Msg3 1240 may be providedby at least one higher layer (e.g. RRC) parameter. A UE may transmit arandom access preamble via PRACH and Msg3 1240 via PUSCH on a same cell.A base station may indicate an UL BWP for a PUSCH transmission of Msg31240 via system information block. A UE may employ HARQ for aretransmission of Msg 3 1240.

In an example, multiple UEs may perform Msg 1 1220 by transmitting asame preamble to a base station and receive, from the base station, asame random access response comprising an identity (e.g., TC-RNTI).Contention resolution 1250 may ensure that a UE does not incorrectly usean identity of another UE. For example, contention resolution 1250 maybe based on C-RNTI on PDCCH or a UE contention resolution identity onDL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UEmay perform contention resolution 1250 based on a reception of a PDCCHtransmission that is addressed to the C-RNTI. In response to detectionof a C-RNTI on a PDCCH, a UE may consider contention resolution 1250successful and may consider a random access procedure successfullycompleted. If a UE has no valid C-RNTI, a contention resolution may beaddressed by employing a TC-RNTI. For example, if a MAC PDU issuccessfully decoded and a MAC PDU comprises a UE contention resolutionidentity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, a UEmay consider the contention resolution 1250 successful and may considerthe random access procedure successfully completed.

FIG. 13 is an example structure for MAC entities as per an aspect of anembodiment. In an example, a wireless device may be configured tooperate in a multi-connectivity mode. A wireless device in RRC_CONNECTEDwith multiple RX/TX may be configured to utilize radio resourcesprovided by multiple schedulers located in a plurality of base stations.The plurality of base stations may be connected via a non-ideal or idealbackhaul over the Xn interface. In an example, a base station in aplurality of base stations may act as a master base station or as asecondary base station. A wireless device may be connected to one masterbase station and one or more secondary base stations. A wireless devicemay be configured with multiple MAC entities, e.g. one MAC entity formaster base station, and one or more other MAC entities for secondarybase station(s). In an example, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 illustrates an examplestructure for MAC entities when MCG and SCG are configured for awireless device.

In an example, at least one cell in a SCG may have a configured UL CC,wherein a cell of at least one cell may be called PSCell or PCell ofSCG, or sometimes may be simply called PCell. A PSCell may be configuredwith PUCCH resources. In an example, when a SCG is configured, there maybe at least one SCG bearer or one split bearer. In an example, upondetection of a physical layer problem or a random access problem on aPSCell, or upon reaching a number of RLC retransmissions associated withthe SCG, or upon detection of an access problem on a PSCell during a SCGaddition or a SCG change: an RRC connection re-establishment proceduremay not be triggered, UL transmissions towards cells of an SCG may bestopped, a master base station may be informed by a UE of a SCG failuretype and DL data transfer over a master base station may be maintained.

In an example, a MAC sublayer may provide services such as data transferand radio resource allocation to upper layers (e.g. 1310 or 1320). A MACsublayer may comprise a plurality of MAC entities (e.g. 1350 and 1360).A MAC sublayer may provide data transfer services on logical channels.To accommodate different kinds of data transfer services, multiple typesof logical channels may be defined. A logical channel may supporttransfer of a particular type of information. A logical channel type maybe defined by what type of information (e.g., control or data) istransferred. For example, BCCH, PCCH, CCCH and DCCH may be controlchannels and DTCH may be a traffic channel. In an example, a first MACentity (e.g. 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCHand MAC control elements. In an example, a second MAC entity (e.g. 1320)may provide services on BCCH, DCCH, DTCH and MAC control elements.

A MAC sublayer may expect from a physical layer (e.g. 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,signaling of scheduling request or measurements (e.g. CQI). In anexample, in dual connectivity, two MAC entities may be configured for awireless device: one for MCG and one for SCG. A MAC entity of wirelessdevice may handle a plurality of transport channels. In an example, afirst MAC entity may handle first transport channels comprising a PCCHof MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one ormore first UL-SCHs of MCG and one or more first RACHs of MCG. In anexample, a second MAC entity may handle second transport channelscomprising a second BCH of SCG, one or more second DL-SCHs of SCG, oneor more second UL-SCHs of SCG and one or more second RACHs of SCG.

In an example, if a MAC entity is configured with one or more SCells,there may be multiple DL-SCHs and there may be multiple UL-SCHs as wellas multiple RACHs per MAC entity. In an example, there may be one DL-SCHand UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero orone UL-SCH and zero or one RACH for an SCell. A DL-SCH may supportreceptions using different numerologies and/or TTI duration within a MACentity. A UL-SCH may also support transmissions using differentnumerologies and/or TTI duration within the MAC entity.

In an example, a MAC sublayer may support different functions and maycontrol these functions with a control (e.g. 1355 or 1365) element.Functions performed by a MAC entity may comprise mapping between logicalchannels and transport channels (e.g., in uplink or downlink),multiplexing (e.g. 1352 or 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TB) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g. 1352 or 1362) of MAC SDUs to one or different logical channelsfrom transport blocks (TB) delivered from the physical layer ontransport channels (e.g., in downlink), scheduling information reporting(e.g., in uplink), error correction through HARQ in uplink or downlink(e.g. 1363), and logical channel prioritization in uplink (e.g. 1351 or1361). A MAC entity may handle a random access process (e.g. 1354 or1364).

FIG. 14 is an example diagram of a RAN architecture comprising one ormore base stations. In an example, a protocol stack (e.g. RRC, SDAP,PDCP, RLC, MAC, and PHY) may be supported at a node. A base station(e.g. gNB 120A or 120B) may comprise a base station central unit (CU)(e.g. gNB-CU 1420A or 1420B) and at least one base station distributedunit (DU) (e.g. gNB-DU 1430A, 1430B, 1430C, or 1430D) if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g. CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. In an example, an Xn interface may be configuredbetween base station CUs.

In an example, a base station CU may comprise an RRC function, an SDAPlayer, and a PDCP layer, and base station DUs may comprise an RLC layer,a MAC layer, and a PHY layer. In an example, various functional splitoptions between a base station CU and base station DUs may be possibleby locating different combinations of upper protocol layers (RANfunctions) in a base station CU and different combinations of lowerprotocol layers (RAN functions) in base station DUs. A functional splitmay support flexibility to move protocol layers between a base stationCU and base station DUs depending on service requirements and/or networkenvironments.

In an example, functional split options may be configured per basestation, per base station CU, per base station DU, per UE, per bearer,per slice, or with other granularities. In per base station CU split, abase station CU may have a fixed split option, and base station DUs maybe configured to match a split option of a base station CU. In per basestation DU split, a base station DU may be configured with a differentsplit option, and a base station CU may provide different split optionsfor different base station DUs. In per UE split, a base station (basestation CU and at least one base station DUs) may provide differentsplit options for different wireless devices. In per bearer split,different split options may be utilized for different bearers. In perslice splice, different split options may be applied for differentslices.

FIG. 15 is an example diagram showing RRC state transitions of awireless device. In an example, a wireless device may be in at least oneRRC state among an RRC connected state (e.g. RRC_Connected 1530,RRC_Connected), an RRC idle state (e.g. RRC_Idle 1510, RRC_Idle), and/oran RRC inactive state (e.g. RRC_Inactive 1520, RRC_Inactive). In anexample, in an RRC connected state, a wireless device may have at leastone RRC connection with at least one base station (e.g. gNB and/or eNB),which may have a UE context of the wireless device. A UE context (e.g. awireless device context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an example, in an RRC idle state, a wireless device may nothave an RRC connection with a base station, and a UE context of awireless device may not be stored in a base station. In an example, inan RRC inactive state, a wireless device may not have an RRC connectionwith a base station. A UE context of a wireless device may be stored ina base station, which may be called as an anchor base station (e.g. lastserving base station).

In an example, a wireless device may transition a UE RRC state betweenan RRC idle state and an RRC connected state in both ways (e.g.connection release 1540 or connection establishment 1550; or connectionreestablishment) and/or between an RRC inactive state and an RRCconnected state in both ways (e.g. connection inactivation 1570 orconnection resume 1580). In an example, a wireless device may transitionits RRC state from an RRC inactive state to an RRC idle state (e.g.connection release 1560).

In an example, an anchor base station may be a base station that maykeep a UE context (a wireless device context) of a wireless device atleast during a time period that a wireless device stays in a RANnotification area (RNA) of an anchor base station, and/or that awireless device stays in an RRC inactive state. In an example, an anchorbase station may be a base station that a wireless device in an RRCinactive state was lastly connected to in a latest RRC connected stateor that a wireless device lastly performed an RNA update procedure in.In an example, an RNA may comprise one or more cells operated by one ormore base stations. In an example, a base station may belong to one ormore RNAs. In an example, a cell may belong to one or more RNAs.

In an example, a wireless device may transition a UE RRC state from anRRC connected state to an RRC inactive state in a base station. Awireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

In an example, an anchor base station may broadcast a message (e.g. RANpaging message) to base stations of an RNA to reach to a wireless devicein an RRC inactive state, and/or the base stations receiving the messagefrom the anchor base station may broadcast and/or multicast anothermessage (e.g. paging message) to wireless devices in their coveragearea, cell coverage area, and/or beam coverage area associated with theRNA through an air interface.

In an example, when a wireless device in an RRC inactive state movesinto a new RNA, the wireless device may perform an RNA update (RNAU)procedure, which may comprise a random access procedure by the wirelessdevice and/or a UE context retrieve procedure. A UE context retrieve maycomprise: receiving, by a base station from a wireless device, a randomaccess preamble; and fetching, by a base station, a UE context of thewireless device from an old anchor base station. Fetching may comprise:sending a retrieve UE context request message comprising a resumeidentifier to the old anchor base station and receiving a retrieve UEcontext response message comprising the UE context of the wirelessdevice from the old anchor base station.

In an example embodiment, a wireless device in an RRC inactive state mayselect a cell to camp on based on at least a on measurement results forone or more cells, a cell where a wireless device may monitor an RNApaging message and/or a core network paging message from a base station.In an example, a wireless device in an RRC inactive state may select acell to perform a random access procedure to resume an RRC connectionand/or to transmit one or more packets to a base station (e.g. to anetwork). In an example, if a cell selected belongs to a different RNAfrom an RNA for a wireless device in an RRC inactive state, the wirelessdevice may initiate a random access procedure to perform an RNA updateprocedure. In an example, if a wireless device in an RRC inactive statehas one or more packets, in a buffer, to transmit to a network, thewireless device may initiate a random access procedure to transmit oneor more packets to a base station of a cell that the wireless deviceselects. A random access procedure may be performed with two messages(e.g. 2 stage random access) and/or four messages (e.g. 4 stage randomaccess) between the wireless device and the base station.

In an example embodiment, a base station receiving one or more uplinkpackets from a wireless device in an RRC inactive state may fetch a UEcontext of a wireless device by transmitting a retrieve UE contextrequest message for the wireless device to an anchor base station of thewireless device based on at least one of an AS context identifier, anRNA identifier, a base station identifier, a resume identifier, and/or acell identifier received from the wireless device. In response tofetching a UE context, a base station may transmit a path switch requestfor a wireless device to a core network entity (e.g. AMF, MME, and/orthe like). A core network entity may update a downlink tunnel endpointidentifier for one or more bearers established for the wireless devicebetween a user plane core network entity (e.g. UPF, S-GW, and/or thelike) and a RAN node (e.g. the base station), e.g. changing a downlinktunnel endpoint identifier from an address of the anchor base station toan address of the base station.

A gNB may communicate with a wireless device via a wireless networkemploying one or more new radio technologies. The one or more radiotechnologies may comprise at least one of: multiple technologies relatedto physical layer; multiple technologies related to medium accesscontrol layer; and/or multiple technologies related to radio resourcecontrol layer. Example embodiments of enhancing the one or more radiotechnologies may improve performance of a wireless network. Exampleembodiments may increase the system throughput, or data rate oftransmission. Example embodiments may reduce battery consumption of awireless device. Example embodiments may improve latency of datatransmission between a gNB and a wireless device. Example embodimentsmay improve network coverage of a wireless network. Example embodimentsmay improve transmission efficiency of a wireless network.

A gNB may transmit one or more MAC PDUs to a wireless device. In anexample, a MAC PDU may be a bit string that is byte aligned (e.g., amultiple of eight bits) in length. In an example, bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table. More generally, the bitstring may be read from left to right and then in the reading order ofthe lines. In an example, the bit order of a parameter field within aMAC PDU is represented with the first and most significant bit in theleftmost bit and the last and least significant bit in the rightmostbit.

In an example, a MAC SDU may be a bit string that is byte aligned (e.g.,a multiple of eight bits) in length. In an example, a MAC SDU may beincluded in a MAC PDU from the first bit onward.

In an example, a MAC CE may be a bit string that is byte aligned (e.g.,a multiple of eight bits) in length.

In an example, a MAC subheader may be a bit string that is byte aligned(e.g., a multiple of eight bits) in length. In an example, a MACsubheader may be placed immediately in front of a corresponding MAC SDU,MAC CE, or padding.

In an example, a MAC entity may ignore a value of reserved bits in a DLMAC PDU.

In an example, a MAC PDU may comprise one or more MAC subPDUs. A MACsubPDU of the one or more MAC subPDUs may comprise: a MAC subheader only(including padding); a MAC subhearder and a MAC SDU; a MAC subheader anda MAC CE; and/or a MAC subheader and padding. In an example, the MAC SDUmay be of variable size. In an example, a MAC subhearder may correspondto a MAC SDU, a MAC CE, or padding.

In an example, when a MAC subheader corresponds to a MAC SDU, avariable-sized MAC CE, or padding, the MAC subheader may comprise: an Rfield with a one bit length; an F field with a one bit length; an LCIDfield with a multi-bit length; and/or an L field with a multi-bitlength.

FIG. 16A shows an example of a MAC subheader with an R field, an Ffield, an LCID field, and an L field. In the example MAC subheader ofFIG. 16A, the LCID field may be six bits in length, and the L field maybe eight bits in length. FIG. 16B shows example of a MAC subheader withan R field, a F field, an LCID field, and an L field. In the example MACsubheader of FIG. 16B, the LCID field may be six bits in length, and theL field may be sixteen bits in length.

In an example, when a MAC subheader corresponds to a fixed sized MAC CEor padding, the MAC subheader may comprise: an R field with a two bitlength and an LCID field with a multi-bit length. FIG. 16C shows anexample of a MAC subheader with an R field and an LCID field. In theexample MAC subheader of FIG. 16C, the LCID field may be six bits inlength, and the R field may be two bits in length.

FIG. 17A shows an example of a DL MAC PDU. In the example of FIG. 17A,multiple MAC CEs, such as MAC CE 1 and 2, may be placed together. A MACsubPDU comprising a MAC CE may be placed before any MAC subPDUcomprising a MAC SDU or a MAC subPDU comprising padding.

FIG. 17B shows an example of a UL MAC PDU. In the example of FIG. 17B,multiple MAC CEs, such as MAC CE 1 and 2, may be placed together. A MACsubPDU comprising a MAC CE may be placed after all MAC subPDUscomprising a MAC SDU. In addition, the MAC subPDU may be placed before aMAC subPDU comprising padding.

In an example, a MAC entity of a gNB may transmit one or more MAC CEs toa MAC entity of a wireless device. FIG. 18 shows an example of multipleLCIDs that may be associated with the one or more MAC CEs. In theexample of FIG. 18, the one or more MAC CEs comprise at least one of: aSP ZP CSI-RS Resource Set Activation/Deactivation MAC CE; a PUCCHspatial relation Activation/Deactivation MAC CE; a SP SRSActivation/Deactivation MAC CE; a SP CSI reporting on PUCCHActivation/Deactivation MAC CE; a TCI State Indication for UE-specificPDCCH MAC CE; a TCI State Indication for UE-specific PDSCH MAC CE; anAperiodic CSI Trigger State Subselection MAC CE; a SP CSI-RS/CSI-IMResource Set Activation/Deactivation MAC CE; a UE contention resolutionidentity MAC CE; a timing advance command MAC CE; a DRX command MAC CE;a Long DRX command MAC CE; an SCell activation/deactivation MAC CE (1Octet); an SCell activation/deactivation MAC CE (4 Octet); and/or aduplication activation/deactivation MAC CE. In an example, a MAC CE,such as a MAC CE transmitted by a MAC entity of a gNB to a MAC entity ofa wireless device, may have an LCID in the MAC subheader correspondingto the MAC CE. Different MAC CE may have different LCID in the MACsubheader corresponding to the MAC CE. For example, an LCID given by111011 in a MAC subheader may indicate that a MAC CE associated with theMAC subheader is a long DRX command MAC CE.

In an example, the MAC entity of the wireless device may transmit to theMAC entity of the gNB one or more MAC CEs. FIG. 19 shows an example ofthe one or more MAC CEs. The one or more MAC CEs may comprise at leastone of: a short buffer status report (BSR) MAC CE; a long BSR MAC CE; aC-RNTI MAC CE; a configured grant confirmation MAC CE; a single entryPHR MAC CE; a multiple entry PHR MAC CE; a short truncated BSR; and/or along truncated BSR. In an example, a MAC CE may have an LCID in the MACsubheader corresponding to the MAC CE. Different MAC CE may havedifferent LCID in the MAC subheader corresponding to the MAC CE. Forexample, an LCID given by 111011 in a MAC subheader may indicate that aMAC CE associated with the MAC subheader is a short-truncated commandMAC CE.

In carrier aggregation (CA), two or more component carriers (CCs) may beaggregated. A wireless device may simultaneously receive or transmit onone or more CCs, depending on capabilities of the wireless device, usingthe technique of CA. In an example, a wireless device may support CA forcontiguous CCs and/or for non-contiguous CCs. CCs may be organized intocells. For example, CCs may be organized into one primary cell (PCell)and one or more secondary cells (SCells).

When configured with CA, a wireless device may have one RRC connectionwith a network. During an RRC connectionestablishment/re-establishment/handover, a cell providing NAS mobilityinformation may be a serving cell. During an RRC connectionre-establishment/handover procedure, a cell providing a security inputmay be a serving cell. In an example, the serving cell may denote aPCell. In an example, a gNB may transmit, to a wireless device, one ormore messages comprising configuration parameters of a plurality of oneor more SCells, depending on capabilities of the wireless device.

When configured with CA, a base station and/or a wireless device mayemploy an activation/deactivation mechanism of an SCell to improvebattery or power consumption of the wireless device. When a wirelessdevice is configured with one or more SCells, a gNB may activate ordeactivate at least one of the one or more SCells. Upon configuration ofan SCell, the SCell may be deactivated unless an SCell state associatedwith the SCell is set to “activated” or “dormant”.

In an example, a wireless device may activate/deactivate an SCell inresponse to receiving an SCell Activation/Deactivation MAC CE.

In an example, a gNB may transmit, to a wireless device, one or moremessages comprising an SCell timer (e.g., sCellDeactivationTimer). In anexample, a wireless device may deactivate an SCell in response to anexpiry of the SCell timer.

When a wireless device receives an SCell Activation/Deactivation MAC CEactivating an SCell, the wireless device may activate the SCell. Inresponse to the activating the SCell, the wireless device may performoperations comprising: SRS transmissions on the SCell; CQI/PMI/RI/CRIreporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoringfor the SCell; and/or PUCCH transmissions on the SCell.

In an example, in response to the activating the SCell, the wirelessdevice may start or restart a first SCell timer (e.g.,sCellDeactivationTimer) associated with the SCell. The wireless devicemay start or restart the first SCell timer in the slot when the SCellActivation/Deactivation MAC CE activating the SCell has been received.In an example, in response to the activating the SCell, the wirelessdevice may (re-)initialize one or more suspended configured uplinkgrants of a configured grant Type 1 associated with the SCell accordingto a stored configuration. In an example, in response to the activatingthe SCell, the wireless device may trigger PHR.

When a wireless device receives an SCell Activation/Deactivation MAC CEdeactivating an activated SCell, the wireless device may deactivate theactivated SCell. In an example, when a first SCell timer (e.g.,sCellDeactivationTimer) associated with an activated SCell expires, thewireless device may deactivate the activated SCell. In response to thedeactivating the activated SCell, the wireless device may stop the firstSCell timer associated with the activated SCell. In an example, inresponse to the deactivating the activated SCell, the wireless devicemay clear one or more configured downlink assignments and/or one or moreconfigured uplink grants of a configured uplink grant Type 2 associatedwith the activated SCell. In an example, in response to the deactivatingthe activated SCell, the wireless device may: suspend one or moreconfigured uplink grants of a configured uplink grant Type 1 associatedwith the activated SCell; and/or flush HARQ buffers associated with theactivated SCell.

In an example, when an SCell is deactivated, a wireless device may notperform operations comprising: transmitting SRS on the SCell; reportingCQI/PMI/RI/CRI for the SCell; transmitting on UL-SCH on the SCell;transmitting on RACH on the SCell; monitoring at least one first PDCCHon the SCell; monitoring at least one second PDCCH for the SCell; and/ortransmitting a PUCCH on the SCell.

In an example, when at least one first PDCCH on an activated SCellindicates an uplink grant or a downlink assignment, a wireless devicemay restart a first SCell timer (e.g., sCellDeactivationTimer)associated with the activated SCell. In an example, when at least onesecond PDCCH on a serving cell (e.g. a PCell or an SCell configured withPUCCH, i.e. PUCCH SCell) scheduling the activated SCell indicates anuplink grant or a downlink assignment for the activated SCell, awireless device may restart the first SCell timer (e.g.,sCellDeactivationTimer) associated with the activated SCell.

In an example, when an SCell is deactivated, if there is an ongoingrandom access procedure on the SCell, a wireless device may abort theongoing random access procedure on the SCell.

FIG. 20A shows an example of an SCell Activation/Deactivation MAC CE ofone octet. A first MAC PDU subheader with a first LCID (e.g., ‘111010’as shown in FIG. 18) may identify the SCell Activation/Deactivation MACCE of one octet. The SCell Activation/Deactivation MAC CE of one octetmay have a fixed size. The SCell Activation/Deactivation MAC CE of oneoctet may comprise a single octet. The single octet may comprise a firstnumber of C-fields (e.g. seven) and a second number of R-fields (e.g.,one).

FIG. 20B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID (e.g.,‘111001’ as shown in FIG. 18) may identify the SCellActivation/Deactivation MAC CE of four octets. The SCellActivation/Deactivation MAC CE of four octets may have a fixed size. TheSCell Activation/Deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third number of C-fields (e.g.,31) and a fourth number of R-fields (e.g., 1).

In FIG. 20A and/or FIG. 20B, a C_(i) field may indicate anactivation/deactivation status of an SCell with an SCell index i if anSCell with SCell index i is configured. In an example, when the C_(i)field is set to one, an SCell with an SCell index i may be activated. Inan example, when the C_(i) field is set to zero, an SCell with an SCellindex i may be deactivated. In an example, if there is no SCellconfigured with SCell index i, the wireless device may ignore the C_(i)field. In FIG. 20A and FIG. 20B, an R field may indicate a reserved bit.The R field may be set to zero.

When configured with CA, a base station and/or a wireless device mayemploy a hibernation mechanism for an SCell to improve battery or powerconsumption of the wireless device and/or to improve latency of SCellactivation/addition. When the wireless device hibernates the SCell, theSCell may be transitioned into a dormant state. In response to the SCellbeing transitioned into a dormant state, the wireless device may: stoptransmitting SRS on the SCell; report CQI/PMI/RI/PTI/CRI for the SCellaccording to a periodicity configured for the SCell in a dormant state;not transmit on UL-SCH on the SCell; not transmit on RACH on the SCell;not monitor the PDCCH on the SCell; not monitor the PDCCH for the SCell;and/or not transmit PUCCH on the SCell. In an example, reporting CSI foran SCell and not monitoring the PDCCH on/for the SCell, when the SCellis in a dormant state, may provide the base station an always-updatedCSI for the SCell. With the always-updated CSI, the base station mayemploy a quick and/or accurate channel adaptive scheduling on the SCellonce the SCell is transitioned back into active state, thereby speedingup the activation procedure of the SCell. In an example, reporting CSIfor the SCell and not monitoring the PDCCH on/for the SCell, when theSCell is in dormant state, may improve battery or power consumption ofthe wireless device, while still providing the base station timelyand/or accurate channel information feedback. In an example, aPCell/PSCell and/or a PUCCH secondary cell may not be configured ortransitioned into dormant state.

When configured with one or more SCells, a gNB may activate, hibernate,or deactivate at least one of the one or more SCells. In an example, agNB may transmit one or more RRC messages comprising parametersindicating at least one SCell being set to an active state, a dormantstate, or an inactive state, to a wireless device.

In an example, when an SCell is in an active state, the wireless devicemay perform: SRS transmissions on the SCell; CQI/PMI/RI/CRI reportingfor the SCell; PDCCH monitoring on the SCell; PDCCH monitoring for theSCell; and/or PUCCH/SPUCCH transmissions on the SCell.

In an example, when an SCell is in an inactive state, the wirelessdevice may: not transmit SRS on the SCell; not report CQI/PMI/RI/CRI forthe SCell; not transmit on UL-SCH on the SCell; not transmit on RACH onthe SCell; not monitor PDCCH on the SCell; not monitor PDCCH for theSCell; and/or not transmit PUCCH/SPUCCH on the SCell.

In an example, when an SCell is in a dormant state, the wireless devicemay: not transmit SRS on the SCell; report CQI/PMI/RI/CRI for the SCell;not transmit on UL-SCH on the SCell; not transmit on RACH on the SCell;not monitor PDCCH on the SCell; not monitor PDCCH for the SCell; and/ornot transmit PUCCH/SPUCCH on the SCell.

When configured with one or more SCells, a gNB may activate, hibernate,or deactivate at least one of the one or more SCells. In an example, agNB may transmit one or more MAC control elements comprising parametersindicating activation, deactivation, or hibernation of at least oneSCell to a wireless device.

In an example, a gNB may transmit a first MAC CE (e.g.,activation/deactivation MAC CE, as shown in FIG. 20A or FIG. 20B)indicating activation or deactivation of at least one SCell to awireless device. In FIG. 20A and/or FIG. 20B, a C_(i) field may indicatean activation/deactivation status of an SCell with an SCell index i ifan SCell with SCell index i is configured. In an example, when the C_(i)field is set to one, an SCell with an SCell index i may be activated. Inan example, when the C_(i) field is set to zero, an SCell with an SCellindex i may be deactivated. In an example, if there is no SCellconfigured with SCell index i, the wireless device may ignore the C_(i)field. In FIG. 20A and FIG. 20B, an R field may indicate a reserved bit.In an example, the R field may be set to zero.

In an example, a gNB may transmit a second MAC CE (e.g., hibernation MACCE) indicating activation or hibernation of at least one SCell to awireless device. In an example, the second MAC CE may be associated witha second LCID different from a first LCID of the first MAC CE (e.g.,activation/deactivation MAC CE). In an example, the second MAC CE mayhave a fixed size. In an example, the second MAC CE may consist of asingle octet containing seven C-fields and one R-field. FIG. 21A showsan example of the second MAC CE with a single octet. In another example,the second MAC CE may consist of four octets containing 31 C-fields andone R-field. FIG. 21B shows an example of the second MAC CE with fouroctets. In an example, the second MAC CE with four octets may beassociated with a third LCID different from the second LCID for thesecond MAC CE with a single octet, and/or the first LCID foractivation/deactivation MAC CE. In an example, when there is no SCellwith a serving cell index greater than 7, the second MAC CE of one octetmay be applied, otherwise the second MAC CE of four octets may beapplied.

In an example, when the second MAC CE is received, and the first MAC CEis not received, C_(i) may indicate a dormant/activated status of anSCell with SCell index i if there is an SCell configured with SCellindex i, otherwise the MAC entity may ignore the C_(i) field. In anexample, when C_(i) is set to “1”, the wireless device may transition anSCell associated with SCell index i into a dormant state. In an example,when C_(i) is set to “0”, the wireless device may activate an SCellassociated with SCell index i. In an example, when C_(i) is set to “0”and the SCell with SCell index i is in a dormant state, the wirelessdevice may activate the SCell with SCell index i. In an example, when Cis set to “0” and the SCell with SCell index i is not in a dormantstate, the wireless device may ignore the C_(i) field.

In an example, when both the first MAC CE (activation/deactivation MACCE) and the second MAC CE (hibernation MAC CE) are received, two C_(i)fields of the two MAC CEs may indicate possible state transitions of theSCell with SCell index i if there is an SCell configured with SCellindex i, otherwise the MAC entity may ignore the C_(i) fields. In anexample, the C_(i) fields of the two MAC CEs may be interpretedaccording to FIG. 21C.

When configured with one or more SCells, a gNB may activate, hibernate,or deactivate at least one of the one or more SCells. In an example, aMAC entity of a gNB and/or a wireless device may maintain an SCelldeactivation timer (e.g., sCellDeactivationTimer) per configured SCell(except the SCell configured with PUCCH/SPUCCH, if any) and deactivatethe associated SCell upon its expiry.

In an example, a MAC entity of a gNB and/or a wireless device maymaintain an SCell hibernation timer (e.g., sCellHibernationTimer) perconfigured SCell (except the SCell configured with PUCCH/SPUCCH, if any)and hibernate the associated SCell upon the SCell hibernation timerexpiry if the SCell is in active state. In an example, when both theSCell deactivation timer and the SCell hibernation timer are configured,the SCell hibernation timer may take priority over the SCelldeactivation timer. In an example, when both the SCell deactivationtimer and the SCell hibernation timer are configured, a gNB and/or awireless device may ignore the SCell deactivation timer regardless ofthe SCell deactivation timer expiry.

In an example, a MAC entity of a gNB and/or a wireless device maymaintain a dormant SCell deactivation timer (e.g.,dormantSCellDeactivationTimer) per configured SCell (except the SCellconfigured with PUCCH/SPUCCH, if any), and deactivate the associatedSCell upon the dormant SCell deactivation timer expiry if the SCell isin dormant state.

In an example, when a MAC entity of a wireless device is configured withan activated SCell upon SCell configuration, the MAC entity may activatethe SCell. In an example, when a MAC entity of a wireless devicereceives a MAC CE(s) activating an SCell, the MAC entity may activatethe SCell. In an example, the MAC entity may start or restart the SCelldeactivation timer associated with the SCell in response to activatingthe SCell. In an example, the MAC entity may start or restart the SCellhibernation timer (if configured) associated with the SCell in responseto activating the SCell. In an example, the MAC entity may trigger PHRprocedure in response to activating the SCell.

In an example, when a MAC entity of a wireless device receives a MACCE(s) indicating deactivating an SCell, the MAC entity may deactivatethe SCell. In an example, in response to receiving the MAC CE(s), theMAC entity may: deactivate the SCell; stop an SCell deactivation timerassociated with the SCell; and/or flush all HARQ buffers associated withthe SCell.

In an example, when an SCell deactivation timer associated with anactivated SCell expires and an SCell hibernation timer is notconfigured, the MAC entity may: deactivate the SCell; stop the SCelldeactivation timer associated with the SCell; and/or flush all HARQbuffers associated with the SCell.

In an example, when a first PDCCH on an activated SCell indicates anuplink grant or downlink assignment, or a second PDCCH on a serving cellscheduling an activated SCell indicates an uplink grant or a downlinkassignment for the activated SCell, or a MAC PDU is transmitted in aconfigured uplink grant or received in a configured downlink assignment,the MAC entity may: restart the SCell deactivation timer associated withthe SCell; and/or restart the SCell hibernation timer associated withthe SCell if configured. In an example, when an SCell is deactivated, anongoing random access procedure on the SCell may be aborted.

In an example, when a MAC entity is configured with an SCell associatedwith an SCell state set to dormant state upon the SCell configuration,or when the MAC entity receives MAC CE(s) indicating transitioning theSCell into a dormant state, the MAC entity may: transition the SCellinto a dormant state; transmit one or more CSI reports for the SCell;stop an SCell deactivation timer associated with the SCell; stop anSCell hibernation timer associated with the SCell if configured; startor restart a dormant SCell deactivation timer associated with the SCell;and/or flush all HARQ buffers associated with the SCell. In an example,when the SCell hibernation timer associated with the activated SCellexpires, the MAC entity may: hibernate the SCell; stop the SCelldeactivation timer associated with the SCell; stop the SCell hibernationtimer associated with the SCell; and/or flush all HARQ buffersassociated with the SCell. In an example, when a dormant SCelldeactivation timer associated with a dormant SCell expires, the MACentity may: deactivate the SCell; and/or stop the dormant SCelldeactivation timer associated with the SCell. In an example, when anSCell is in dormant state, ongoing random access procedure on the SCellmay be aborted.

FIG. 22 shows DCI formats for an example of 20 MHz FDD operation with 2Tx antennas at the base station and no carrier aggregation in an LTEsystem. In a NR system, the DCI formats may comprise at least one of:DCI format 0_0/0_1 indicating scheduling of PUSCH in a cell; DCI format1_0/1_1 indicating scheduling of PDSCH in a cell; DCI format 2_0notifying a group of UEs of slot format; DCI format 2_1 notifying agroup of UEs of PRB(s) and OFDM symbol(s) where a UE may assume notransmission is intended for the UE; DCI format 2_2 indicatingtransmission of TPC commands for PUCCH and PUSCH; and/or DCI format 2_3indicating transmission of a group of TPC commands for SRS transmissionby one or more UEs. In an example, a gNB may transmit a DCI via a PDCCHfor scheduling decision and power-control commends. More specifically,the DCI may comprise at least one of: downlink scheduling assignments,uplink scheduling grants, power-control commands. The downlinkscheduling assignments may comprise at least one of: PDSCH resourceindication, transport format, HARQ information, and control informationrelated to multiple antenna schemes, a command for power control of thePUCCH used for transmission of ACK/NACK in response to downlinkscheduling assignments. The uplink scheduling grants may comprise atleast one of: PUSCH resource indication, transport format, and HARQrelated information, a power control command of the PUSCH.

In an example, the different types of control information correspond todifferent DCI message sizes. For example, supporting spatialmultiplexing with noncontiguous allocation of RBs in the frequencydomain may require a larger scheduling message in comparison with anuplink grant allowing for frequency-contiguous allocation only. The DCImay be categorized into different DCI formats, where a formatcorresponds to a certain message size and usage.

In an example, a UE may monitor one or more PDCCH candidates to detectone or more DCI with one or more DCI format. The one or more PDCCH maybe transmitted in common search space or UE-specific search space. A UEmay monitor PDCCH with only a limited set of DCI format, to save powerconsumption. For example, a normal UE may not be required to detect aDCI with DCI format 6 which is used for an eMTC UE. The more DCI formatto be detected, the more power be consumed at the UE.

In an example, the one or more PDCCH candidates that a UE monitors maybe defined in terms of PDCCH UE-specific search spaces. A PDCCHUE-specific search space at CCE aggregation level Lϵ{1, 2, 4, 8} may bedefined by a set of PDCCH candidates for CCE aggregation level L. In anexample, for a DCI format, a UE may be configured per serving cell byone or more higher layer parameters a number of PDCCH candidates per CCEaggregation level L.

In an example, in non-DRX mode operation, a UE may monitor one or morePDCCH candidate in control resource set q according to a periodicity ofW_(PDDCH, q) symbols that may be configured by one or more higher layerparameters for control resource set q.

In an example, the information in the DCI formats used for downlinkscheduling may be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator (0 or 3 bits), RBallocation; HARQ process number; MCS, NDI, and RV (for the first TB);MCS, NDI and RV (for the second TB); MIMO related information; PDSCHresource-element mapping and QCI; Downlink assignment index (DAI); TPCfor PUCCH; SRS request (1 bit), triggering one-shot SRS transmission;ACK/NACK offset; DCI format 0/1A indication, used to differentiatebetween DCI format 1A and 0; and padding if necessary. The MIMO relatedinformation may comprise at least one of: PMI, precoding information,transport block swap flag, power offset between PDSCH and referencesignal, reference-signal scrambling sequence, number of layers, and/orantenna ports for the transmission.

In an example, the information in the DCI formats used for uplinkscheduling may be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator, resourceallocation type, RB allocation; MCS, NDI (for the first TB); MCS, NDI(for the second TB); phase rotation of the uplink DMRS; precodinginformation; CSI request, requesting an aperiodic CSI report; SRSrequest (2 bit), used to trigger aperiodic SRS transmission using one ofup to three preconfigured settings; uplink index/DAI; TPC for PUSCH; DCIformat 0/1A indication; and padding if necessary.

In an example, a gNB may perform cyclic redundancy check (CRC)scrambling for a DCI, before transmitting the DCI via a PDCCH. The gNBmay perform CRC scrambling by bit-wise addition (or Modulo-2 addition orexclusive OR (XOR) operation) of multiple bits of at least one wirelessdevice identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI,TPC-PUSCH-RNTI, SP CSI C-RNTI, SRS-TPC-RNTI, INT-RNTI, SFI-RNTI, P-RNTI,SI-RNTI, RA-RNTI, and/or MCS-C-RNTI) with the CRC bits of the DCI. Thewireless device may check the CRC bits of the DCI, when detecting theDCI. The wireless device may receive the DCI when the CRC is scrambledby a sequence of bits that is the same as the at least one wirelessdevice identifier.

In a NR system, in order to support wide bandwidth operation, a gNB maytransmit one or more PDCCH in different control resource sets. A gNB maytransmit one or more RRC message comprising configuration parameters ofone or more control resource sets. At least one of the one or morecontrol resource sets may comprise at least one of: a first OFDM symbol;a number of consecutive OFDM symbols; a set of resource blocks; aCCE-to-REG mapping; and a REG bundle size, in case of interleavedCCE-to-REG mapping.

A base station (gNB) may configure a wireless device (UE) with uplink(UL) bandwidth parts (BWPs) and downlink (DL) BWPs to enable bandwidthadaptation (BA) on a PCell. If carrier aggregation is configured, thegNB may further configure the UE with at least DL BWP(s) (i.e., theremay be no UL BWPs in the UL) to enable BA on an SCell. For the PCell, aninitial active BWP may be a first BWP used for initial access. For theSCell, a first active BWP may be a second BWP configured for the UE tooperate on the SCell upon the SCell being activated.

In paired spectrum (e.g. FDD), a gNB and/or a UE may independentlyswitch a DL BWP and an UL BWP. In unpaired spectrum (e.g. TDD), a gNBand/or a UE may simultaneously switch a DL BWP and an UL BWP.

In an example, a gNB and/or a UE may switch a BWP between configuredBWPs by means of a DCI or a BWP inactivity timer. When the BWPinactivity timer is configured for a serving cell, the gNB and/or the UEmay switch an active BWP to a default BWP in response to an expiry ofthe BWP inactivity timer associated with the serving cell. The defaultBWP may be configured by the network.

In an example, for FDD systems, when configured with BA, one UL BWP foreach uplink carrier and one DL BWP may be active at a time in an activeserving cell. In an example, for TDD systems, one DL/UL BWP pair may beactive at a time in an active serving cell. Operating on the one UL BWPand the one DL BWP (or the one DL/UL pair) may improve UE batteryconsumption. BWPs other than the one active UL BWP and the one active DLBWP that the UE may work on may be deactivated. On deactivated BWPs, theUE may: not monitor PDCCH; and/or not transmit on PUCCH, PRACH, andUL-SCH.

In an example, a serving cell may be configured with at most a firstnumber (e.g., four) of BWPs. In an example, for an activated servingcell, there may be one active BWP at any point in time.

In an example, a BWP switching for a serving cell may be used toactivate an inactive BWP and deactivate an active BWP at a time. In anexample, the BWP switching may be controlled by a PDCCH indicating adownlink assignment or an uplink grant. In an example, the BWP switchingmay be controlled by a BWP inactivity timer (e.g., bwp-InactivityTimer).In an example, the BWP switching may be controlled by a MAC entity inresponse to initiating a Random Access procedure. Upon addition of anSpCell or activation of an SCell, one BWP may be initially activewithout receiving a PDCCH indicating a downlink assignment or an uplinkgrant. The active BWP for a serving cell may be indicated by RRC and/orPDCCH. In an example, for unpaired spectrum, a DL BWP may be paired witha UL BWP, and BWP switching may be common for both UL and DL.

FIG. 23 shows an example of BWP switching on an SCell. In an example, aUE may receive RRC message comprising parameters of a SCell and one ormore BWP configuration associated with the SCell. The RRC message maycomprise: RRC connection reconfiguration message (e.g.,RRCReconfiguration); RRC connection reestablishment message (e.g., RR CRestablishment); and/or RRC connection setup message (e.g., RRCSetup).Among the one or more BWPs, at least one BWP may be configured as thefirst active BWP (e.g., BWP 1 in FIG. 23), one BWP as the default BWP(e.g., BWP 0 in FIG. 23). The UE may receive a MAC CE to activate theSCell at n^(th) slot. The UE may start a SCell deactivation timer (e.g.,sCellDeactivationTimer), and start CSI related actions for the SCell,and/or start CSI related actions for the first active BWP of the SCell.The UE may start monitoring a PDCCH on BWP 1 in response to activatingthe SCell.

In an example, the UE may start restart a BWP inactivity timer (e.g.,bwp-InactivityTimer) at m^(th) slot in response to receiving a DCIindicating DL assignment on BWP 1. The UE may switch back to the defaultBWP (e.g., BWP 0) as an active BWP when the BWP inactivity timerexpires, at s^(th) slot. The UE may deactivate the SCell and/or stop theBWP inactivity timer when the sCellDeactivationTimer expires.

Employing the BWP inactivity timer may further reduce UE's powerconsumption when the UE is configured with multiple cells with each cellhaving wide bandwidth (e.g., 1 GHz). The UE may only transmit on orreceive from a narrow-bandwidth BWP (e.g., 5 MHz) on the PCell or SCellwhen there is no activity on an active BWP.

In an example, a MAC entity may apply normal operations on an active BWPfor an activated serving cell configured with a BWP comprising:transmitting on UL-SCH; transmitting on RACH; monitoring a PDCCH;transmitting PUCCH; receiving DL-SCH; and/or (re-) initializing anysuspended configured uplink grants of configured grant Type 1 accordingto a stored configuration, if any.

In an example, on an inactive BWP for each activated serving cellconfigured with a BWP, a MAC entity may: not transmit on UL-SCH; nottransmit on RACH; not monitor a PDCCH; not transmit PUCCH; not transmitSRS, not receive DL-SCH; clear any configured downlink assignment andconfigured uplink grant of configured grant Type 2; and/or suspend anyconfigured uplink grant of configured Type 1.

In an example, if a MAC entity receives a PDCCH for a BWP switching of aserving cell while a Random Access procedure associated with thisserving cell is not ongoing, a UE may perform the BWP switching to a BWPindicated by the PDCCH.

In an example, if a bandwidth part indicator field is configured in DCIformat 1_1, the bandwidth part indicator field value may indicate theactive DL BWP, from the configured DL BWP set, for DL receptions. In anexample, if a bandwidth part indicator field is configured in DCI format0_1, the bandwidth part indicator field value may indicate the active ULBWP, from the configured UL BWP set, for UL transmissions.

In an example, for a primary cell, a UE may be provided by a higherlayer parameter Default-DL-BWP a default DL BWP among the configured DLBWPs. If a UE is not provided a default DL BWP by the higher layerparameter Default-DL-BWP, the default DL BWP is the initial active DLBWP.

In an example, a UE may be provided by higher layer parameterbwp-InactivityTimer, a timer value for the primary cell. If configured,the UE may increment the timer, if running, every interval of 1millisecond for frequency range 1 or every 0.5 milliseconds forfrequency range 2 if the UE may not detect a DCI format 1_1 for pairedspectrum operation or if the UE may not detect a DCI format 1_1 or DCIformat 0_1 for unpaired spectrum operation during the interval.

In an example, if a UE is configured for a secondary cell with higherlayer parameter Default-DL-BWP indicating a default DL BWP among theconfigured DL BWPs and the UE is configured with higher layer parameterbwp-InactivityTimer indicating a timer value, the UE procedures on thesecondary cell may be same as on the primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a UE is configured by higher layer parameterActive-BWP-DL-SCell a first active DL BWP and by higher layer parameterActive-BWP-UL-SCell a first active UL BWP on a secondary cell orcarrier, the UE may use the indicated DL BWP and the indicated UL BWP onthe secondary cell as the respective first active DL BWP and firstactive UL BWP on the secondary cell or carrier.

In an example, a wireless device may transmit one or more uplink controlinformation (UCI) via one or more PUCCH resources to a base station. Theone or more UCI may comprise at least one of: HARQ-ACK information;scheduling request (SR); and/or CSI report. In an example, a PUCCHresource may be identified by at least: frequency location (e.g.,starting PRB); and/or a PUCCH format associated with initial cyclicshift of a base sequence and time domain location (e.g., starting symbolindex). In an example, a PUCCH format may be PUCCH format 0, PUCCHformat 1, PUCCH format 2, PUCCH format 3, or PUCCH format 4. A PUCCHformat 0 may have a length of 1 or 2 OFDM symbols and be less than orequal to 2 bits. A PUCCH format 1 may occupy a number between 4 and 14of OFDM symbols and be less than or equal to 2 bits. A PUCCH format 2may occupy 1 or 2 OFDM symbols and be greater than 2 bits. A PUCCHformat 3 may occupy a number between 4 and 14 of OFDM symbols and begreater than 2 bits. A PUCCH format 4 may occupy a number between 4 and14 of OFDM symbols and be greater than 2 bits. The PUCCH resource may beconfigured on a PCell, or a PUCCH secondary cell.

In an example, when configured with multiple uplink BWPs, a base stationmay transmit to a wireless device, one or more RRC messages comprisingconfiguration parameters of one or more PUCCH resource sets (e.g., atmost 4 sets) on an uplink BWP of the multiple uplink BWPs. Each PUCCHresource set may be configured with a PUCCH resource set index, a listof PUCCH resources with each PUCCH resource being identified by a PUCCHresource identifier (e.g., pucch-Resourceid), and/or a maximum number ofUCI information bits a wireless device may transmit using one of theplurality of PUCCH resources in the PUCCH resource set.

In an example, when configured with one or more PUCCH resource sets, awireless device may select one of the one or more PUCCH resource setsbased on a total bit length of UCI information bits (e.g., HARQ-ARQbits, SR, and/or CSI) the wireless device will transmit. In an example,when the total bit length of UCI information bits is less than or equalto 2, the wireless device may select a first PUCCH resource set with thePUCCH resource set index equal to “0”. In an example, when the total bitlength of UCI information bits is greater than 2 and less than or equalto a first configured value, the wireless device may select a secondPUCCH resource set with the PUCCH resource set index equal to “1”. In anexample, when the total bit length of UCI information bits is greaterthan the first configured value and less than or equal to a secondconfigured value, the wireless device may select a third PUCCH resourceset with the PUCCH resource set index equal to “2”. In an example, whenthe total bit length of UCI information bits is greater than the secondconfigured value and less than or equal to a third value (e.g., 1706),the wireless device may select a fourth PUCCH resource set with thePUCCH resource set index equal to “3”.

In an example, a wireless device may determine, based on a number ofuplink symbols of UCI transmission and a number of UCI bits, a PUCCHformat from a plurality of PUCCH formats comprising PUCCH format 0,PUCCH format 1, PUCCH format 2, PUCCH format 3 and/or PUCCH format 4. Inan example, the wireless device may transmit UCI in a PUCCH using PUCCHformat 0 if the transmission is over 1 symbol or 2 symbols and thenumber of HARQ-ACK information bits with positive or negative SR(HARQ-ACK/SR bits) is 1 or 2. In an example, the wireless device maytransmit UCI in a PUCCH using PUCCH format 1 if the transmission is over4 or more symbols and the number of HARQ-ACK/SR bits is 1 or 2. In anexample, the wireless device may transmit UCI in a PUCCH using PUCCHformat 2 if the transmission is over 1 symbol or 2 symbols and thenumber of UCI bits is more than 2. In an example, the wireless devicemay transmit UCI in a PUCCH using PUCCH format 3 if the transmission isover 4 or more symbols, the number of UCI bits is more than 2 and PUCCHresource does not include an orthogonal cover code. In an example, thewireless device may transmit UCI in a PUCCH using PUCCH format 4 if thetransmission is over 4 or more symbols, the number of UCI bits is morethan 2 and the PUCCH resource includes an orthogonal cover code.

In an example, in order to transmit HARQ-ACK information on a PUCCHresource, a wireless device may determine the PUCCH resource from aPUCCH resource set. The PUCCH resource set may be determined asmentioned above. The wireless device may determine the PUCCH resourcebased on a PUCCH resource indicator field in a DCI (e.g., with a DCIformat 1_0 or DCI for 1_1) received on a PDCCH. A 3-bit PUCCH resourceindicator field in the DCI may indicate one of eight PUCCH resources inthe PUCCH resource set. The wireless device may transmit the HARQ-ACKinformation in a PUCCH resource indicated by the 3-bit PUCCH resourceindicator field in the DCI.

In an example, the wireless device may transmit one or more UCI bits viaa PUCCH resource of an active uplink BWP of a PCell or a PUCCH secondarycell. Since at most one active uplink BWP in a cell is supported for awireless device, the PUCCH resource indicated in the DCI is naturally aPUCCH resource on the active uplink BWP of the cell.

In an example, DRX operation may be used by a wireless device (UE) toimprove UE battery lifetime. In an example, in DRX, UE maydiscontinuously monitor downlink control channel, e.g., PDCCH or EPDCCH.In an example, the base station may configure DRX operation with a setof DRX parameters, e.g., using RRC configuration. The set of DRXparameters may be selected based on the application type such that thewireless device may reduce power and resource consumption. In anexample, in response to DRX being configured/activated, a UE may receivedata packets with an extended delay, since the UE may be in DRXSleep/Off state at the time of data arrival at the UE and the basestation may wait until the UE transitions to the DRX ON state.

In an example, during a DRX mode, the UE may power down most of itscircuitry when there are no packets to be received. The UE may monitorPDCCH discontinuously in the DRX mode. The UE may monitor the PDCCHcontinuously when a DRX operation is not configured. During this timethe UE listens to the downlink (DL) (or monitors PDCCHs) which is calledDRX Active state. In a DRX mode, a time during which UE doesn'tlisten/monitor PDCCH is called DRX Sleep state.

FIG. 24 shows an example of the embodiment. A gNB may transmit an RRCmessage comprising one or more DRX parameters of a DRX cycle. The one ormore parameters may comprise a first parameter and/or a secondparameter. The first parameter may indicate a first time value of theDRX Active state (e.g., DRX On duration) of the DRX cycle. The secondparameter may indicate a second time of the DRX Sleep state (e.g., DRXOff duration) of the DRX cycle. The one or more parameters may furthercomprise a time duration of the DRX cycle. During the DRX Active state,the UE may monitor PDCCHs for detecting one or more DCIs on a servingcell. During the DRX Sleep state, the UE may stop monitoring PDCCHs onthe serving cell. When multiple cells are in active state, the UE maymonitor all PDCCHs on (or for) the multiple cells during the DRX Activestate. During the DRX off duration, the UE may stop monitoring all PDCCHon (or for) the multiple cells. The UE may repeat the DRX operationsaccording to the one or more DRX parameters.

In an example, DRX may be beneficial to the base station. In an example,if DRX is not configured, the wireless device may be transmittingperiodic CSI and/or SRS frequently (e.g., based on the configuration).With DRX, during DRX OFF periods, the UE may not transmit periodic CSIand/or SRS. The base station may assign these resources to the other UEsto improve resource utilization efficiency.

In an example, the MAC entity may be configured by RRC with a DRXfunctionality that controls the UE's downlink control channel (e.g.,PDCCH) monitoring activity for a plurality of RNTIs for the MAC entity.The plurality of RNTIs may comprise at least one of: C-RNTI; CS-RNTI;INT-RNTI; SP-CSI-RNTI; SFI-RNTI; TPC-PUCCH-RNTI; TPC-PUSCH-RNTI;Semi-Persistent Scheduling C-RNTI; eIMTA-RNTI; SL-RNTI; SL-V-RNTI;CC-RNTI; or SRS-TPC-RNTI. In an example, in response to being inRRC_CONNECTED, if DRX is configured, the MAC entity may monitor thePDCCH discontinuously using the DRX operation; otherwise the MAC entitymay monitor the PDCCH continuously.

In an example, RRC may control DRX operation by configuring a pluralityof timers. The plurality of timers may comprise: a DRX On duration timer(e.g., drx-onDurationTimer); a DRX inactivity timer (e.g.,drx-InactivityTimer); a downlink DRX HARQ RTT timer (e.g.,drx-HARQ-RTT-TimerDL); an uplink DRX HARQ RTT Timer (e.g.,drx-HARQ-RTT-TimerUL); a downlink retransmission timer (e.g.,drx-RetransmissionTimerDL); an uplink retransmission timer (e.g.,drx-RetransmissionTimerUL); one or more parameters of a short DRXconfiguration (e.g., drx-ShortCycle and/or drx-ShortCycleTimer)) and oneor more parameters of a long DRX configuration (e.g., drx-LongCycle). Inan example, time granularity for DRX timers may be in terms of PDCCHsubframes (e.g., indicated as psf in the DRX configurations), or interms of milliseconds.

In an example, in response to a DRX cycle being configured, the ActiveTime may include the time while at least one timer is running. The atleast one timer may comprise drx-onDurationTimer, drx-InactivityTimer,drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, ormac-ContentionResolutionTimer.

In an example, drx-Inactivity-Timer may specify a time duration forwhich the UE may be active after successfully decoding a PDCCHindicating a new transmission (UL or DL or SL). In an example, thistimer may be restarted upon receiving PDCCH for a new transmission (ULor DL or SL). In an example, the UE may transition to a DRX mode (e.g.,using a short DRX cycle or a long DRX cycle) in response to the expiryof this timer.

In an example, drx-ShortCycle may be a first type of DRX cycle (e.g., ifconfigured) that needs to be followed when UE enters DRX mode. In anexample, a DRX-Config IE indicates the length of the short cycle.

In an example, drx-ShortCycleTimer may be expressed as multiples ofshortDRX-Cycle. The timer may indicate the number of initial DRX cyclesto follow the short DRX cycle before entering the long DRX cycle.

In an example, drx-onDurationTimer may specify the time duration at thebeginning of a DRX Cycle (e.g., DRX ON). In an example,drx-onDurationTimer may indicate the time duration before entering thesleep mode (DRX OFF).

In an example, drx-HARQ-RTT-TimerDL may specify a minimum duration fromthe time new transmission is received and before the UE may expect aretransmission of a same packet. In an example, this timer may be fixedand may not be configured by RRC.

In an example, drx-RetransmissionTimerDL may indicate a maximum durationfor which UE may be monitoring PDCCH when a retransmission from theeNodeB is expected by the UE.

In an example, in response to a DRX cycle being configured, the ActiveTime may comprise the time while a Scheduling Request is sent on PUCCHand is pending.

In an example, in response to a DRX cycle being configured, the ActiveTime may comprise the time while an uplink grant for a pending HARQretransmission can occur and there is data in the corresponding HARQbuffer for synchronous HARQ process.

In an example, in response to a DRX cycle being configured, the ActiveTime may comprise the time while a PDCCH indicating a new transmissionaddressed to the C-RNTI of the MAC entity has not been received aftersuccessful reception of a Random Access Response for the preamble notselected by the MAC entity.

In an example, DRX may be configured for a wireless device. A DL HARQRTT Timer may expire in a subframe and the data of the correspondingHARQ process may not be successfully decoded. The MAC entity may startthe drx-RetransmissionTimerDL for the corresponding HARQ process.

In an example, DRX may be configured for a wireless device. An UL HARQRTT Timer may expire in a subframe. The MAC entity may start thedrx-RetransmissionTimerUL for the corresponding HARQ process.

In an example, DRX may be configured for a wireless device. A DRXCommand MAC control element or a Long DRX Command MAC control elementmay be received. The MAC entity may stop drx-onDurationTimer and stopdrx-InactivityTimer.

In an example, DRX may be configured for a wireless device. In anexample, drx-InactivityTimer may expire or a DRX Command MAC controlelement may be received in a subframe. In an example, in response toShort DRX cycle being configured, the MAC entity may start or restartdrx-ShortCycleTimer and may use Short DRX Cycle. Otherwise, the MACentity may use the Long DRX cycle.

In an example, DRX may be configured for a wireless device. In anexample, drx-ShortCycle Timer may expire in a subframe. The MAC entitymay use the Long DRX cycle.

In an example, DRX may be configured for a wireless device. In anexample, a Long DRX Command MAC control element may be received. The MACentity may stop drx-ShortCycleTimer and may use the Long DRX cycle.

In an example, DRX may be configured for a wireless device. In anexample, if the Short DRX Cycle is used and [(SFN*10)+subframe number]modulo (drx-ShortCycle)=(drxStartOffset) modulo (drx-ShortCycle), thewireless device may start drx-onDurationTimer.

In an example, DRX may be configured for a wireless device. In anexample, if the Long DRX Cycle is used and [(SFN*10)+subframe number]modulo (drx-longCycle)=drxStartOffset, the wireless device may startdrx-onDurationTimer.

FIG. 25 shows example of DRX operation in a legacy system. A basestation may transmit an RRC message comprising configuration parametersof DRX operation. A base station may transmit to a UE, a first DCI via aPDCCH for assignment of downlink resources. The UE may start thedrx-InactivityTimer during which, the UE may monitor the PDCCH and/orreceiving a transport block (TB) on the downlink resources. Afterreceiving the TB, the UE may start a HARQ RTT Timer (e.g.,drx-HARQ-RTT-TimerDL), during which, the UE may stop monitoring thePDCCH. The UE may transmit a NACK to the base station upon unsuccessfulreceiving the TB. When the HARQ RTT Timer expires, the UE may monitorthe PDCCH and start a HARQ retransmission timer (e.g.,drx-RetransmissionTimerDL). When the HARQ retransmission timer isrunning, the UE may receive a second DCI indicating a DL grant for theretransmission of the TB. If not receiving the second DCI before theHARQ retransmission timer expires, the UE may stop monitoring the PDCCH.

Similarly, for uplink transmission, the base station may transmit afirst DCI for an uplink grant via a PDCCH, to the UE. The UE may startthe drx-InactivityTimer during which, the UE may monitor the PDCCH.After transmitting a TB via the uplink grant, the UE may start a HARQRTT Timer (e.g., drx-HARQ-RTT-TimerUL), during which, the UE may stopmonitoring the PDCCH. The base station may transmit a NACK to the UEupon unsuccessful receiving the TB. When the HARQ RTT Timer (e.g.,drx-HARQ-RTT-TimerUL) expires, the UE may start a HARQ retransmissiontimer (e.g., drx-RetransmissionTimerUL) and monitor the PDCCH for theNACK. When the HARQ retransmission timer is running, the UE may receivea second DCI indicating an uplink grant for the retransmission of theTB. If not receiving the second DCI before the HARQ retransmission timerexpires, the UE may stop monitoring the PDCCH.

In an example, a wireless device may receive an uplink grant dynamicallyon a PDCCH or in a random access response (RAR). The wireless device mayreceive an uplink grant configured semi-persistently by a radio resourcecontrol (RRC) message. The wireless device may transmit, via the uplinkgrant, an uplink transport block (TB) on an uplink shared channel(UL-SCH). To transmit the uplink transport block, a medium accesscontrol (MAC) layer of the wireless device may receive one or more HARQinformation from lower layers (e.g., physical layer) of the wirelessdevice. The one or more HARQ information may comprise at least one of:HARQ process identifier (ID); new data indicator (NDI); redundancyversion (RV); and/or transport block size (TBS).

In an example, if a MAC entity of a wireless device has a C-RNTI, aTemporary C-RNTI (TC-RNTI), or a configured scheduling RNTI (CS-RNTI),for each PDCCH occasion and for each serving cell belonging to a timealignment group (TAG) that has a running timeAlignmentTimer and for eachuplink grant received for the PDCCH occasion, if the uplink grant forthe serving Cell has been received on the PDCCH for the MAC entity'sC-RNTI or TC-RNTI, the MAC entity may deliver the uplink grant and oneor more associated HARQ information to the HARQ entity.

In an example, a MAC entity of a wireless device may comprise a HARQentity for each serving cell with configured uplink (e.g., comprising acase when the wireless device is configured with a supplementaryuplink). The HARQ entity may maintain a number of parallel HARQprocesses. Each HARQ process of the number of parallel HARQ processesmay support one TB, and the HARQ process may be associated with a HARQprocess identifier (ID). For UL transmission with UL grant in RAResponse, HARQ process identifier 0 may be used.

In an example, when a MAC entity of a wireless device is configured withPUSCH repetition (e.g., pusch-AggregationFactor>1), the parameterpusch-AggregationFactor may provide a number of transmissions of a TBwithin a bundle of a dynamic grant. After the initial transmission,pusch-AggregationFactor−1 HARQ retransmissions may follow within abundle. When the MAC entity is configured with repK>1, the parameterrepK may provide a number of transmissions of a TB within a bundle of aconfigured uplink grant. After the initial transmission, HARQretransmissions may follow within a bundle. For both dynamic grant andconfigured uplink grant, bundling operation may rely on the HARQ entityfor invoking the same HARQ process for each transmission that is part ofthe same bundle. Within a bundle, HARQ retransmissions may be triggeredwithout waiting for feedback from previous transmission according topusch-AggregationFactor for the dynamic grant and repK for theconfigured uplink grant, respectively. Each transmission within a bundlemay be a separate uplink grant after the initial uplink grant within abundle is delivered to the HARQ entity.

In an example, for each transmission within a bundle of a dynamic grant,a sequence of redundancy versions may be determined based on one or morefields of a DCI carrying the dynamic grant. For each transmission withina bundle of a configured uplink grant, a sequence of redundancy versionsmay be determined based on one or more configuration parameters in a RRCmessage.

In an example, for an uplink grant, a HARQ entity of a wireless devicemay identify a HARQ process associated with the uplink grant. For theidentified HARQ process, if the received uplink grant is not addressedto a TC-RNTI on PDCCH, and an NDI provided in the associated HARQinformation has been toggled compared to an NDI value in the previoustransmission of the TB of the HARQ process, the HARQ entity may obtain aMAC PDU to transmit from a multiplexing and assembly entity. In responseto obtaining the MAC PDU, the HARQ entity may deliver the MAC PDU, theuplink grant, and the HARQ information of the TB to the identified HARQprocess and instruct the identified HARQ process to trigger a newtransmission. In an example, for the identified HARQ process, if thereceived uplink grant is addressed to a TC-RNTI on PDCCH, or the NDIprovided in the associated HARQ information has not been toggledcompared to the NDI value in the previous transmission of the TB of theHARQ process, the HARQ entity may deliver the uplink grant and the HARQinformation (e.g., redundancy version) of the TB to the identified HARQprocess, and instruct the identified HARQ process to trigger aretransmission.

In an example, a HARQ process may be associated with a HARQ buffer. Awireless device may perform a new transmission on a resource and with amodulation coding scheme (MCS) indicated on either a PDCCH, a RAR, or aRRC message. In an example, the wireless device may perform aretransmission on a resource and (if provided) with a MCS indicated onPDCCH, or on a same resource and with a same MCS as was used for lastmade transmission attempt within a bundle.

In an example, if a HARQ entity requests a new transmission of a TB, aHARQ process may store the MAC PDU in an associated HARQ buffer, storethe uplink grant received from the HARQ entity, and generate atransmission for the TB. If the HARQ entity requests a retransmissionfor a TB, the HARQ process may store the uplink grant received from theHARQ entity and generate a transmission for the TB. In an example, togenerate a transmission for a TB, the HARQ process may instruct thephysical layer to generate a transmission according to the stored uplinkgrant if the MAC PDU was obtained from a Msg3 buffer or if there is nomeasurement gap at the time of the transmission and, in case ofretransmission, if the retransmission does not collide with atransmission for the MAC PDU obtained from the Msg3 buffer.

FIG. 26 shows an example of uplink TB retransmission mechanism based onHARQ procedure. In an example, a base station (e.g., gNB in FIG. 26) maytransmit to a wireless device (e.g., UE in FIG. 26), a first downlinkcontrol information (DCI) comprising an uplink grant and one or moreHARQ information. The one or more HARQ information may comprise a HARQprocess ID (e.g., Process ID=k as shown in FIG. 26), a first NDI value(e.g., 1^(st) NDI=1). The UE, before receiving the first DCI, may have acurrent NDI value (e.g., Current NDI=0 as shown in FIG. 26). In responseto receiving the first DCI, the UE may determine that the first NDI hasbeen toggled in response to the first NDI value (1) being different fromthe current NDI value (0). In response to the first NDI being toggled, aHARQ entity of the wireless device may obtain a MAC PDU from amultiplexing and assembly entity of the wireless device. The HARQ entitymay deliver the MAC PDU, the uplink grant, and the one or more HARQinformation to a HARQ process, where the HARQ process is identified bythe HARQ process ID (e.g., Process ID=k as shown in FIG. 26). The HARQentity may instruct the HARQ process to trigger a new transmission for aTB comprising the MAC PDU. The HARQ process may store the MAC PDU in anassociated HARQ buffer and store the uplink grant. The HARQ process mayinstruct a physical layer of the wireless device to generate a newtransmission for the TB according to the stored uplink grant. As shownin FIG. 26, the physical layer may transmit the TB according to thestored uplink grant. In an example, the gNB may provide a subsequentuplink grant to the UE for a retransmission of the TB when the gNB doesnot successfully receive the TB transmitted by the UE. The gNB maytransmit a second DCI indicating the retransmission, where the secondDCI comprises a same HARQ process ID as the first HARQ process ID, asecond uplink grant, a RV value, and a second NDI value (e.g., 2^(nd)NDI=1). The UE may determine the second NDI is not toggled in responseto the second NDI value (1) being equal to the first NDI value (1),which is now the new Current NDI value. In response to the second NDInot being toggled, the HARQ entity may deliver, to a HARQ processidentified by the HARQ process ID=k, the second uplink grant and the RVvalue, and the HARQ entity may instruct the HARQ process to trigger aretransmission of the TB. The HARQ process may store the second uplinkgrant. The HARQ process may instruct the physical layer of the wirelessdevice to generate a retransmission for the TB according to the seconduplink grant. As shown in FIG. 26, the physical layer may retransmit theTB according to the second uplink grant.

FIG. 27 shows an example of uplink TB transmission mechanism based onHARQ procedure. In an example, a base station (e.g., gNB in FIG. 27) maytransmit to a wireless device (e.g., UE in FIG. 27), a first DCIcomprising an uplink grant and one or more HARQ information. The one ormore HARQ information may comprise a HARQ process ID (e.g., Process ID=kas shown in FIG. 27) and a first NDI value (e.g., 1^(st) NDI=1). The UE,before receiving the first DCI, may have a current NDI value (e.g.,Current NDI=0 as shown in FIG. 27). In response to receiving the firstDCI, the UE may determine that the first NDI has been toggled inresponse to the first NDI value (1) being different from the current NDIvalue (0). In response to the first NDI being toggled, a HARQ entity ofthe wireless device may obtain a MAC PDU from a multiplexing andassembly entity of the wireless device. The HARQ entity may deliver theMAC PDU, the uplink grant and the one or more HARQ information to a HARQprocess, where the HARQ process is identified by the HARQ process ID(e.g., Process ID=k as shown in FIG. 27). The HARQ entity may instructthe HARQ process to trigger a new transmission for a first TB comprisingthe MAC PDU. The HARQ process may store the MAC PDU in an associatedHARQ buffer and store the uplink grant. The HARQ process may instruct aphysical layer of the wireless device to generate a new transmission forthe first TB according to the stored uplink grant. As shown in FIG. 27,the physical layer may transmit the first TB according to the storeduplink grant. In an example, the gNB may provide a subsequent uplinkgrant to the UE for transmitting a second TB after the gNB successfullyreceives the first TB. The gNB may transmit a second DCI indicating thenew transmission, where the second DCI comprises a same HARQ process IDas the first HARQ process ID, a second uplink grant, a RV value, and asecond NDI value (e.g., 0 as shown in FIG. 27). The UE may determine thesecond NDI is toggled in response to the second NDI value (0) beingdifferent from the first NDI value (1), which is now the new Current NDIvalue. In response to the second NDI being toggled, a HARQ entity of thewireless device may obtain a second MAC PDU from the multiplexing andassembly entity. The HARQ entity may deliver the second MAC PDU, thesecond uplink grant, and one or more second HARQ information to the HARQprocess (e.g., identified by Process ID=k). The HARQ entity may instructthe HARQ process to trigger a new transmission for the second TBcomprising the second MAC PDU. The HARQ process may store the second MACPDU in an associated HARQ buffer and store the second uplink grant. TheHARQ process may instruct the physical layer to generate a newtransmission for the second TB according to the second uplink grant. Asshown in FIG. 27, the physical layer may transmit the second TBaccording to the second uplink grant.

In an example, a wireless system (e.g., 4G or 5G) may support multipletypes of services, where different UEs may transmit different datapackets for the different services. The multiple types of services maycomprise at least one of: an ultra-reliable low-latency communication(URLLC); an enhanced mobile broadband service (eMBB); a machine typecommunication (MTC); and a vehicle to vehicle (or vehicle to everything)communication (V2X). In an example, a first data packet (e.g., a URLLCdata packet) of a first wireless device may be multiplexed with a seconddata packet (e.g., an eMBB data packet) of a second wireless device on aPUSCH resource. In an example, the first data packet may be transmittedwith a first transmission format (e.g., a first numerology or a firstscheduling granularity) on a first PUSCH resource. In an example, thesecond data packet may be transmitted with a second transmission format(e.g., a second numerology or a second scheduling granularity) on asecond PUSCH resource. In an example, the first PUSCH resource may be apart of the second PUSCH resource. In an example, the second PUSCHresource may be allocated for the second wireless device by an uplinkgrant indicated via a PDCCH. Assuming the first data packet is required(or at least preferred) to be transmitted with a lower latency than thesecond data packet (e.g., given the respective service types associatedwith the first and second data packets), the first data packet of thefirst wireless device may be transmitted on the first PUSCH resourcewhich is a part of the second PUSCH resource. In such case, the basestation may receive data from the second wireless device on the secondPUSCH resource, which may also contain signals (e.g., on the part of thesecond PUSCH resource corresponding to the first PUSCH resource) for thefirst wireless device. In an example, the base station may wronglydetect the second data packet of the second wireless device if there isno mechanism to indicate whether the first data packet was transmittedon the part of the second PUSCH resource allocated to the second datapacket. In order to solve this preemption problem, where higher prioritydata (e.g., URLLC) is multiplexed with and preempts lower priority data(e.g., eMBB data) (or more generally the problem of multiplexing uplinktransmissions with different transmission formats) on a PUSCH, a gNB maytransmit a DCI comprising fields indicating one or more uplinkpre-emption indications to a wireless device (e.g., the second wirelessdevice) or a group of wireless devices (e.g., including the secondwireless device), indicating whether one or more time/frequencyresources are preempted (e.g., reserved for the first wireless device)or not.

FIG. 28 shows an example of uplink pre-emption mechanism. In an example,a base station (e.g., gNB in FIG. 28) may transmit to a wireless device(e.g., UE in FIG. 28), a first DCI comprising a first uplink grant. Theuplink grant may comprise PUSCH resources. In response to the first DCI,the UE may start transmitting a TB on the first uplink grant. As shownin FIG. 28, the UE may receive an uplink pre-emption indication from thebase station. The uplink pre-emption indication may comprise acancellation indication, a stop indication, or a suspending indication.The uplink pre-emption indication may indicate that at least a part ofthe PUSCH resources is pre-empted, or the wireless device may stopuplink transmission on the at least part of the PUSCH resources. Asshown in FIG. 28, in response to the uplink pre-emption indication, thewireless device may stop the ongoing uplink transmission on the at leastpart of the PUSCH resources, wherein the at least part of the PUSCHresources are pre-empted based on the uplink pre-emption indication. Inan example, the base station may transmit a DCI comprising the uplinkpre-emption indication. The DCI may be transmitted to a wireless deviceaddressed by a C-RNTI, or be transmitted to a group of wireless devicesaddressed by a group RNTI. In an example, the base station may transmita MAC CE comprising the uplink pre-emption indication. In an example,the base station may transmit a signal sequence (e.g., a CSI-RS/DMRS)comprising the uplink pre-emption indication. In an example, aftertransmitting the uplink pre-emption indication, the base station maytransmit a second DCI to a second UE (e.g., URLLC UE) indicating asecond uplink grant comprising the at least part of the PUSCH resources,where the PUSCH resources are allocated in the first DCI for the firstUE. The second UE, in response to receiving the second DCI, may transmituplink data via the second uplink grant.

FIG. 29 shows an example of cancellation of scheduled (e.g., not startedyet) uplink transmission based on uplink pre-emption indication. In anexample, a base station (e.g., gNB in FIG. 29) may transmit to awireless device (e.g., UE in FIG. 29), a first DCI comprising a firstuplink grant. The uplink grant may comprise PUSCH resources. In responseto the first DCI, the UE may generate a TB based on the first DCI. Asshown in FIG. 29, the UE, before starting uplink transmission of the TB,may receive an uplink pre-emption indication from the base station. Theuplink pre-emption indication may comprise a cancellation indication, astop indication, or a suspending indication. The uplink pre-emptionindication may indicate that at least a part of the PUSCH resources ispre-empted, or the wireless device may stop uplink transmission on theat least part of the PUSCH resources. As shown in FIG. 29, in responseto the uplink pre-emption indication, the wireless device may stop thescheduled (e.g., not started yet) uplink transmission on the at leastpart of the PUSCH resources, wherein the at least part of the PUSCHresources are pre-empted based on the uplink pre-emption indication. Inan example, the base station may transmit a DCI comprising the uplinkpre-emption indication. The DCI may be transmitted to a wireless deviceaddressed by a C-RNTI, or be transmitted to a group of wireless devicesaddressed by a group RNTI. In an example, the base station may transmita MAC CE comprising the uplink pre-emption indication. In an example,the base station may transmit a signal sequence (e.g., a CSI-RS/DMRS)comprising the uplink pre-emption indication. In an example, aftertransmitting the uplink pre-emption indication, the base station maytransmit a second DCI to a second UE (e.g., URLLC UE) indicating asecond uplink grant comprising the at least part of the PUSCH resources,where the PUSCH resources are allocated in the first DCI for the firstUE. The second UE, in response to receiving the second DCI, may transmituplink data via the second uplink grant.

FIG. 30 shows an example of group uplink cancellation based on uplinkpre-emption indication. In an example, a base station (e.g., gNB in FIG.30) may transmit to a first wireless device (e.g., UE 1 in FIG. 30), afirst DCI comprising a first uplink grant. The first uplink grant maycomprise first PUSCH resources. The gNB may transmit to a secondwireless device (e.g., UE 2 in FIG. 30), a second DCI comprising asecond uplink grant. The second uplink grant may comprise second PUSCHresources. As shown in FIG. 30, the gNB may transmit an uplinkpre-emption indication to UE 1 and UE 2 in a group command DCI.

In an example, UE 1 may receive the pre-emption indication after UE 1starts uplink transmission on the first uplink grant. UE 2 may receivethe uplink pre-emption indication before UE 2 starts uplink transmissionon the second uplink grant.

In an example, the uplink pre-emption indication may comprise acancellation indication, a stop indication, or a suspending indication.In an example, a base station may transmit a DCI comprising the uplinkpre-emption indication. The DCI may be transmitted to a group ofwireless devices (e.g., UE 1 and UE 2) addressed by a group RNTI.

In an example, UE 1 may start uplink transmission on the first uplinkgrant at a first symbol earlier than a second symbol on which uplinktransmission shall be stopped according to the uplink pre-emptionindication.

In an example, the uplink pre-emption indication may indicate uplinktransmission shall be stopped on a first symbol earlier than a secondsymbol on which scheduled uplink transmission of UE 2 may occur.

As shown in FIG. 30, UE 1, after receiving the uplink pre-emptionindication, may stop ongoing uplink transmission on at least first partof the first uplink grant, based on the uplink pre-emption indication.UE 2 may, after receiving the uplink pre-emption indication, may stopscheduled uplink transmission on at least second part of the seconduplink grant, based on the uplink pre-emption indication. The uplinkpre-emption indication may indicate that the at least first part of thefirst uplink grant is pre-empted, and/or the at least second part of thesecond uplink grant is pre-empted. In an example, after transmitting theuplink pre-emption indication, the base station may transmit a third DCIto a third UE (e.g., URLLC UE) indicating a third uplink grantcomprising the at least first part of the first uplink grant and/or theat least second part of the second uplink grant. The third UE, inresponse to receiving the third DCI, may transmit uplink data via thethird uplink grant.

In existing technologies, in response to receiving an uplink pre-emptionindication, a wireless device may cancel uplink transmission (eitherongoing or scheduled) of a TB on an uplink grant (e.g., dynamical orsemi-persistent), where the uplink grant may be received in a first DCIor a RRC message. The wireless device may receive a new uplink grant ina second DCI after canceling the uplink transmission. The wirelessdevice may determine whether a NDI is toggled or not based on a NDIvalue received in the second DCI and a value in a previous transmissionof the TB. Different from a case of downlink pre-emption indication,when the wireless device cancels the uplink transmission of the TB basedon the uplink pre-emption indication, the wireless device, by employingexisting technologies, may have difficulty in determining whether thenew uplink grant in the second DCI is for a new transmission or aretransmission. This is because it is unclear whether the wirelessdevice should treated the cancelled uplink transmission as atransmission which has been performed or whether the wireless deviceshould treated the cancelled uplink transmission as a transmission thathas not been performed. When the wireless device cancels the uplinktransmission of the TB based on the uplink pre-emption indication, thewireless device and the base station, by implementing existingtechnologies, may not align with whether the NDI is toggled or not (or,more generally, whether the cancelled uplink transmission is treated ashaving been performed or not). When not aligned with the base stationregarding whether the NDI is toggled or not, the wireless device maywrongly retransmit a first TB, while the base station actually requiresan initial transmission of a second TB. When not aligned with the basestation regarding whether the NDI is toggled or not, the wireless devicemay wrongly transmit a first TB, while the base station actually isexpecting to receive a retransmission of a second TB. As a result,existing technologies may reduce system throughput, increase datatransmission latency, and/or increase power consumption of the wirelessdevice. There is a need to define the wireless device's behaviour whenreceiving an uplink pre-emption indication, e.g., for the purpose ofcorrectly determining whether the wireless device should perform aretransmission or an initial transmission upon receiving a DCI. Exampleembodiments may align a base station and a wireless device regarding astatus of an uplink HARQ process when uplink pre-emption mechanism issupported for multiplexing different transmissions with differenttransmission formats. Example embodiments may improve system throughput,reduce data transmission latency, and/or reduce power consumption of thewireless device.

FIG. 31 shows an example of enhanced HARQ procedure when uplinkpre-emption indication is supported. In an example, a base station(e.g., gNB in FIG. 31) may transmit to a wireless device (e.g., UE inFIG. 31), a first downlink control information (DCI) comprising anuplink grant and one or more HARQ information. The one or more HARQinformation may comprise a HARQ process ID (e.g., Process ID=k as shownin FIG. 31), a first NDI value (e.g., 1^(st) NDI=1). The wirelessdevice, before receiving the first DCI, may have a current NDI value(e.g., 0 as shown in FIG. 31). In response to receiving the first DCI,the wireless device may determine that the first NDI has been toggled inresponse to the first NDI value (1) being different from the current NDIvalue (0). In response to the first NDI being toggled, a HARQ entity ofthe wireless device may obtain a MAC PDU from a multiplexing andassembly entity of the wireless device. The HARQ entity may deliver theMAC PDU, the uplink grant and the one or more HARQ information to a HARQprocess, where the HARQ process is identified by the HARQ process ID(e.g., Process ID=k as shown in FIG. 31). The HARQ entity may instructthe HARQ process to trigger an initial (or a new) transmission for afirst TB comprising the MAC PDU. The HARQ process may store the MAC PDUin an associated HARQ buffer, and store the uplink grant. The HARQprocess may instruct a physical layer of the wireless device to generatean initial (or a new) transmission for the first TB according to thestored uplink grant.

In an example, as shown in FIG. 31, a physical layer of a wirelessdevice may receive an uplink pre-emption indication from the basestation, before starting a transmission for a first TB according to anuplink grant. The uplink pre-emption indication may indicate that thewireless device may cancel (suspend, or stop) the transmission for thefirst TB on at least one of PUSCH resources of the uplink grant. Inresponse to the uplink pre-emption indication, the physical layer maycancel the transmission for the first TB on the at least one of thePUSCH resources of the uplink grant. In response to cancelling thetransmission for the first TB, a HARQ entity of the wireless device maystore the first NDI value as a current NDI value. The HARQ entity of thewireless device may consider the transmission of the first TB as hasbeen performed by the physical layer, while the physical layer cancelledthe transmission of the first TB in response to the uplink pre-emptionindication.

As shown in FIG. 31, the physical layer of the wireless device mayreceive a second DCI comprising a same HARQ process ID as the first HARQprocess ID, a second uplink grant, a RV value, and a second NDI value(e.g., 1 as shown in FIG. 31). The physical layer may deliver the seconduplink grant and one or more HARQ information (e.g., the first HARQprocess ID, the RV value, and/or the second NDI value) to a MAC layer ofthe wireless device. The MAC entity may deliver the uplink grant and theone or more HARQ information to a HARQ entity of the wireless device.The HARQ entity may identify a HARQ process by the first HARQ processID. The HARQ entity may determine whether a NDI is toggled based on thesecond NDI value and the current NDI value. In an example, as shown inFIG. 31, the HARQ entity may determine that the NDI is not toggled inresponse to the second NDI value (1, as shown in FIG. 31) being same asthe current NDI value, where the current NDI value is a value the HARQentity stores after the wireless device receives the first DCI. Inresponse to the NDI not being toggled, the HARQ entity may instruct theHARQ process to trigger a retransmission of the first TB. The HARQprocess may instruct the physical layer to generate a retransmission ofthe first TB. Accordingly, the physical layer may retransmit the firstTB according to the second uplink grant. The HARQ entity, byimplementing example embodiments, may store a NDI value received beforecancelling uplink transmission in response to an uplink pre-emptionindication. The HARQ entity, by implementing example embodiments, maydetermine a transmission of a TB as has been performed by the physicallayer, while the physical layer has cancelled the uplink transmission inresponse to an uplink pre-emption indication. The HARQ entity, byimplementing example embodiments, may correctly determine whether aninitial transmission or a retransmission is required based on the storedNDI value and a second NDI value, upon the wireless device receives thesecond DCI comprising the second NDI value. Example embodiments mayenable alignment between a base station and a wireless device regardinga status of an uplink HARQ process when uplink pre-emption mechanism issupported for multiplexing different transmissions with differenttransmission formats. Example embodiments may improve system throughput,reduce data transmission latency, and/or reduce power consumption of thewireless device.

FIG. 32 shows an example of enhanced HARQ procedure when uplinkpre-emption indication is supported. In an example, a base station(e.g., gNB in FIG. 32) may transmit to a wireless device (e.g., UE inFIG. 32), a first DCI comprising an uplink grant and one or more HARQinformation. The one or more HARQ information may comprise a HARQprocess ID (e.g., Process ID=k as shown in FIG. 32), a first NDI value(e.g., 1^(st) NDI=1). The wireless device, before receiving the firstDCI, may have a current NDI value (e.g., 0 as shown in FIG. 32). Inresponse to receiving the first DCI, the wireless device may determinethat the first NDI has been toggled in response to the first NDI value(1) being different from the current NDI value (0). In response to thefirst NDI being toggled, a HARQ entity of the wireless device may obtaina MAC PDU from a multiplexing and assembly entity of the wirelessdevice. The HARQ entity may deliver the MAC PDU, the uplink grant andthe one or more HARQ information to a HARQ process, where the HARQprocess is identified by the HARQ process ID (e.g., Process ID=k asshown in FIG. 32). The HARQ entity may instruct the HARQ process totrigger an initial (or a new) transmission for a first TB comprising theMAC PDU. The HARQ process may store the MAC PDU in an associated HARQbuffer, and store the uplink grant. The HARQ process may instruct aphysical layer of the wireless device to generate an initial (or a new)transmission for the first TB according to the stored uplink grant.

In an example, as shown in FIG. 32, a physical layer of a wirelessdevice may receive an uplink pre-emption indication from the basestation, before starting a transmission of a first TB according to anuplink grant. The uplink pre-emption indication may indicate that thewireless device may cancel (suspend, or stop) the transmission of thefirst TB on at least one of PUSCH resources of the uplink grant. Inresponse to the uplink pre-emption indication, the physical layer maycancel the transmission of the first TB on the at least one of the PUSCHresources of the uplink grant. In response to cancelling thetransmission of the first TB, a HARQ entity of the wireless device maystore the first NDI value as a current NDI value. The HARQ entity of thewireless device may consider the transmission of the first TB as havingbeen performed by the physical layer, while the physical layer hascancelled the transmission of the first TB in response to the uplinkpre-emption indication.

As shown in FIG. 32, the physical layer of the wireless device mayreceive a second DCI comprising a same HARQ process ID as the first HARQprocess ID, a second uplink grant, a RV value, and a second NDI value(e.g., 0 as shown in FIG. 32). The physical layer may deliver the seconduplink grant and one or more HARQ information (e.g., the first HARQprocess ID, the RV value, and/or the second NDI value) to a MAC layer ofthe wireless device. The MAC entity may deliver the uplink grant and theone or more HARQ information to a HARQ entity of the wireless device.The HARQ entity may identify a HARQ process by the first HARQ processID. The HARQ entity may determine whether a NDI is toggled based on thesecond NDI value and the current NDI value. In an example, as shown inFIG. 32, the HARQ entity may determine that the NDI is toggled inresponse to the second NDI value (0, as shown in FIG. 32) beingdifferent from the current NDI value, where the current NDI value is avalue the HARQ entity stores after the wireless device receives thefirst DCI. In response to the NDI being toggled, the HARQ entity mayinstruct the HARQ process to trigger an initial (or a new) transmissionof a second TB. The HARQ process may instruct the physical layer togenerate an initial (or a new) transmission of the second TB.Accordingly, the physical layer may transmit the second TB as theinitial (or new) transmission according to the second uplink grant. TheHARQ entity, by implementing example embodiments, may store a NDI valuereceived before cancelling uplink transmission in response to an uplinkpre-emption indication. The HARQ entity, by implementing exampleembodiments, may consider (or determine) a transmission of a TB as hasbeen performed by the physical layer, while the physical layer hascancelled the uplink transmission in response to an uplink pre-emptionindication. The HARQ entity, by implement example embodiments, maycorrectly determine whether an initial transmission or a retransmissionis required based on the stored NDI value and a second NDI value, uponthe wireless device receives the second DCI comprising the second NDIvalue. Example embodiments may enable alignment between a base stationand a wireless device regarding a status of an uplink HARQ process whenuplink pre-emption indication is supported for multiplexing differenttransmissions with different transmission formats. Example embodimentsmay improve system throughput, reduce data transmission latency, and/orreduce power consumption of the wireless device.

FIG. 33 shows an example of enhanced HARQ procedure when uplinkpre-emption indication is supported. In an example, a base station(e.g., gNB in FIG. 33) may transmit to a wireless device (e.g., UE inFIG. 33), a first DCI comprising an uplink grant and one or more HARQinformation. The one or more HARQ information may comprise a HARQprocess ID (e.g., Process ID=k as shown in FIG. 33), a first NDI value(e.g., 1^(st) NDI=1). The wireless device, before receiving the firstDCI, may have a current NDI value (e.g., 0 as shown in FIG. 33). Inresponse to receiving the first DCI, the wireless device may determinethat the first NDI has been toggled in response to the first NDI value(1) being different from the current NDI value (0). In response to thefirst NDI being toggled, a HARQ entity of the wireless device may obtaina MAC PDU from a multiplexing and assembly entity of the wirelessdevice. The HARQ entity may deliver the MAC PDU, the uplink grant andthe one or more HARQ information to a HARQ process, where the HARQprocess is identified by the HARQ process ID (e.g., Process ID=k asshown in FIG. 33). The HARQ entity may instruct the HARQ process totrigger an initial (or a new) transmission for a first TB comprising theMAC PDU. The HARQ process may store the MAC PDU in an associated HARQbuffer, and store the uplink grant. The HARQ process may instruct aphysical layer of the wireless device to generate an initial (or a new)transmission for the first TB according to the stored uplink grant. Asshown in FIG. 33, the physical layer may start the initial (or the new)transmission on PUSCH resources based on the stored uplink grant.

In an example, as shown in FIG. 33, a physical layer of a wirelessdevice may receive an uplink pre-emption indication from the basestation, during a transmission of a first TB on PUSCH resources of anuplink grant. The uplink pre-emption indication may indicate that thewireless device may stop (suspend, or cancel) the transmission of thefirst TB on at least one of the PUSCH resources. In response to theuplink pre-emption indication, the physical layer may stop the ongoingtransmission of the first TB on the at least one of the PUSCH resourcesof the uplink grant. In an example, the physical layer may finish atransmission of a first part of the first TB and may not start atransmission of a second part of the first TB, when the wireless devicereceives the uplink pre-emption indication. The uplink pre-emptionindication may indicate that the wireless device may stop (suspend, orcancel) the transmission of the second part of the first TB on at leastone of the PUSCH resources. In response to stopping the ongoingtransmission of the first TB, a HARQ entity of the wireless device maystore the first NDI value as a current NDI value. The HARQ entity of thewireless device may consider the transmission of the first TB as hasbeen performed by the physical layer, while the physical layer hasfinished a transmission of the first part of the first TB and hasstopped a transmission of the second part of the first TB in response tothe uplink pre-emption indication.

As shown in FIG. 33, the physical layer of the wireless device mayreceive a second DCI comprising a same HARQ process ID as the first HARQprocess ID, a second uplink grant, a RV value, and a second NDI value(e.g., 1 as shown in FIG. 33). The physical layer deliver the seconduplink grant and one or more HARQ information (e.g., the first HARQprocess ID, the RV value, and/or the second NDI value) to a MAC layer ofthe wireless device. The MAC entity may deliver the uplink grant and theone or more HARQ information to a HARQ entity of the wireless device.The HARQ entity may identify a HARQ process by the first HARQ processID. The HARQ entity may determine whether a NDI is toggled based on thesecond NDI value and the current NDI value. In an example, as shown inFIG. 33, the HARQ entity may determine that the NDI is not toggled inresponse to the second NDI value (1, as shown in FIG. 33) being same asthe current NDI value, where the current NDI value is a value the HARQentity stores after the wireless device receives the first DCI. Inresponse to the NDI not being toggled, the HARQ entity may instruct theHARQ process to trigger a retransmission of the first TB. The HARQprocess may instruct the physical layer to generate a retransmission ofthe first TB. Accordingly, the physical layer may retransmit the firstTB according to the second uplink grant. The HARQ entity, byimplementing example embodiments, may store a NDI value received beforestopping an ongoing uplink transmission in response to an uplinkpre-emption indication. The HARQ entity, by implementing exampleembodiments, may consider (or determine) a transmission of a TB as hasbeen performed by the physical layer, while the physical layer hasfinished a transmission of a first part of the TB and has not finished atransmission of a second part of the TB in response to an uplinkpre-emption indication. The HARQ entity, by implement exampleembodiments, may correctly determine whether an initial transmission ora retransmission is required based on the stored NDI value and a secondNDI value, upon the wireless device receives the second DCI comprisingthe second NDI value. Example embodiments may enable alignment between abase station and a wireless device regarding a status of an uplink HARQprocess when uplink pre-emption indication is supported for multiplexingdifferent transmissions with different transmission formats. Exampleembodiments may improve system throughput, reduce data transmissionlatency, and/or reduce power consumption of the wireless device.

FIG. 34 shows an example of enhanced HARQ procedure when uplinkpre-emption indication is supported. In an example, a base station(e.g., gNB in FIG. 34) may transmit to a wireless device (e.g., UE inFIG. 34), a first DCI comprising an uplink grant and one or more HARQinformation. The one or more HARQ information may comprise a HARQprocess ID (e.g., Process ID=k as shown in FIG. 34), a first NDI value(e.g., 1^(st) NDI=1). The wireless device, before receiving the firstDCI, may have a current NDI value (e.g., 0 as shown in FIG. 34). Inresponse to receiving the first DCI, the wireless device may determinethat the first NDI has been toggled in response to the first NDI value(1) being different from the current NDI value (0). In response to thefirst NDI being toggled, a HARQ entity of the wireless device may obtaina MAC PDU from a multiplexing and assembly entity of the wirelessdevice. The HARQ entity may deliver the MAC PDU, the uplink grant andthe one or more HARQ information to a HARQ process, where the HARQprocess is identified by the HARQ process ID (e.g., Process ID=k asshown in FIG. 34). The HARQ entity may instruct the HARQ process totrigger an initial (or a new) transmission of a first TB comprising theMAC PDU. The HARQ process may store the MAC PDU in an associated HARQbuffer, and/or store the uplink grant. The HARQ process may instruct aphysical layer of the wireless device to generate an initial (or a new)transmission of the first TB according to the stored uplink grant. Asshown in FIG. 34, the physical layer may start the initial (or the new)transmission on PUSCH resources based on the stored uplink grant.

In an example, as shown in FIG. 34, a physical layer of a wirelessdevice may receive an uplink pre-emption indication from the basestation, during a transmission of a first TB on PUSCH resources of anuplink grant. The uplink pre-emption indication may indicate that thewireless device may stop (suspend, or cancel) the transmission of thefirst TB on at least one of the PUSCH resources. In response to theuplink pre-emption indication, the physical layer may stop the ongoingtransmission of the first TB on the at least one of the PUSCH resourcesof the uplink grant. In an example, the physical layer may finish atransmission of a first part of the first TB and may not start atransmission of a second part of the first TB, when the wireless devicereceives the uplink pre-emption indication. The uplink pre-emptionindication may indicate that the wireless device may stop (suspend, orcancel) the transmission of the second part of the first TB on at leastone of the PUSCH resources. In response to stopping the ongoingtransmission of the first TB, a HARQ entity of the wireless device maystore the first NDI value as a current NDI value. The HARQ entity of thewireless device may consider the transmission of the first TB as hasbeen performed by the physical layer, while the physical layer hasfinished a transmission of the first part of the first TB and hasstopped a transmission of the second part of the first TB in response tothe uplink pre-emption indication.

As shown in FIG. 34, the physical layer of the wireless device mayreceive a second DCI comprising a same HARQ process ID as the first HARQprocess ID, a second uplink grant, a RV value, and a second NDI value(e.g., 0 as shown in FIG. 34). The physical layer deliver the seconduplink grant and one or more HARQ information (e.g., the first HARQprocess ID, the RV value, and/or the second NDI value) to a MAC layer ofthe wireless device. The MAC entity may deliver the uplink grant and theone or more HARQ information to a HARQ entity of the wireless device.The HARQ entity may identify a HARQ process by the first HARQ processID. The HARQ entity may determine whether a NDI is toggled based on thesecond NDI value and the current NDI value. In an example, as shown inFIG. 34, the HARQ entity may determine that the NDI is toggled inresponse to the second NDI value (0, as shown in FIG. 34) beingdifferent from the current NDI value, where the current NDI value is avalue the HARQ entity stores after the wireless device receives thefirst DCI. In response to the NDI being toggled, the HARQ entity mayinstruct the HARQ process to trigger an initial (or a new) transmissionof a second TB. The second TB may be different from the first TB. TheHARQ process may instruct the physical layer to generate an initial (ora new) transmission of the second TB. Accordingly, the physical layermay transmit the second TB as the initial transmission based on thesecond uplink grant. The HARQ entity, by implementing exampleembodiments, may store a NDI value received before stopping an ongoinguplink transmission in response to an uplink pre-emption indication. TheHARQ entity, by implementing example embodiments, may determine atransmission of a TB as has been performed by the physical layer, whilethe physical layer has finished a transmission of a first part of the TBand has not finished a transmission of a second part of the TB inresponse to an uplink pre-emption indication. The HARQ entity, byimplement example embodiments, may correctly determine whether aninitial transmission or a retransmission is required based on the storedNDI value and a second NDI value, upon the wireless device receives asecond DCI comprising the second NDI value. Example embodiments mayenable alignment between a base station and a wireless device regardinga status of an uplink HARQ process when uplink pre-emption indication issupported for multiplexing different transmissions with differenttransmission formats. Example embodiments may improve system throughput,reduce data transmission latency, and/or reduce power consumption of thewireless device.

In existing technologies, a wireless device may start a bandwidth part(BWP) inactivity timer (e.g., bwp-InactivityTimer) in response toreceiving a DCI comprising an uplink grant. During a time period whenthe bwp-InactivityTimer is running, the wireless device may keep a BWPin active state. When the bwp-InactivityTimer expires, the wirelessdevice may deactivate the BWP, and switch to a default BWP. Similarly,the wireless device may start a secondary cell (SCell) deactivationtimer (e.g., SCellDeactivationTimer) in response to receiving a DCIcomprising an uplink grant. During a time period when theSCellDeactivationTimer is running, the wireless device may keep a SCellin active state. When the SCellDeactivationTimer expires, the wirelessdevice may deactivate the SCell. In an example, the wireless device maystart the bwp-InactivityTimer and/or the SCellDeactivationTimer when thewireless device receives a DCI comprising an uplink grant. The wirelessdevice may receive an uplink pre-emption indication from a base station,during a time period when the bwp-InactivityTimer and/or theSCellDeactivationTimer is running. The wireless device may stop (cancel,or suspend) uplink PUSCH transmission in response to receiving theuplink pre-emption indication. The uplink pre-emption indication mayindicate that the uplink PUSCH transmission shall be stopped. Thewireless device may expect to receive a DCI indicating a retransmission,after stopping the uplink PUSCH transmission. The bwp-InactivityTimerand/or the SCellDeactivationTimer may expires after the wireless devicereceives the uplink pre-emption indication, and/or when the wirelessdevice is expecting to receive the DCI for the retransmission. Thewireless device, by implementing existing technologies, may switch to adefault BWP, or deactivate a SCell, in response to an expiry of thebwp-InactivityTimer and/or in response to an expiry of theSCellDeactivationTimer. Existing technologies may increase datatransmission delay, and/or reduce system throughput. There is a need todefine a wireless device's behavior when receiving an uplink pre-emptionindication, e.g., for the purpose of maintaining an active state of aBWP when the wireless device is expecting a retransmission command.Example embodiments may avoid switching to the default BWP and/ordeactivating the SCell, after the wireless device receives the uplinkpre-emption indication. Example embodiments may improve datatransmission delay and/or system throughput.

FIG. 35 shows an example of improved BWP state management. In anexample, a base station (e.g., gNB in FIG. 35) may transmit to awireless device (e.g., UE in FIG. 35) a first DCI comprising a firstuplink grant. In response to receiving the first DCI, the wirelessdevice may start a BWP inactivity timer (e.g., bwp-InactivityTimer) withan initial timer value. The initial timer value may be indicated in anRRC message. The wireless device may keep a first BWP in active statewhen the bwp-InactivityTimer is running. The wireless device may performone or more actions on the first BWP in response to the first BWP beingin active state, by employing one or more examples of FIG. 23.

In an example, a timer (e.g., bwp-InactivityTimer,SCellDeactivationTimer, or drx-InactivityTimer) may be running once itis started, until it is stopped or until it expires; otherwise the timermay not be running. A timer may be started if it is not running. A timermay be restarted if it is running. A timer may be started or restartedfrom its initial value. In an example, a timer may be implemented as acount-down timer from a first timer value down to a value (e.g., zero).In an example, the timer may be implemented as a count-up timer from avalue (e.g., zero) up to a first timer value. In an example, the timermay be implemented as a down-counter from a first counter value down toa value (e.g., zero). In an example, the timer may be implemented as acount-up counter from a value (e.g., zero) up to a first counter value.

As shown in FIG. 35, based on an uplink grant comprised in the firstDCI, the wireless device may start an initial (or a new) transmission onPUSCH resources on the first BWP. In an example, as shown in FIG. 35,the wireless device may receive an uplink pre-emption indication fromthe base station, during a transmission of a first TB on PUSCH resourcesof the uplink grant. The uplink pre-emption indication may indicate thatthe wireless device may stop (suspend, or cancel) the transmission ofthe first TB on at least one of the PUSCH resources. In response to theuplink pre-emption indication, the physical layer may stop the ongoingtransmission of the first TB on the at least one of the PUSCH resourcesof the uplink grant. In an example, the physical layer may finish atransmission of a first part of the first TB and may not start atransmission of a second part of the first TB, when the wireless devicereceives the uplink pre-emption indication. The uplink pre-emptionindication may indicate that the wireless device may stop (suspend, orcancel) the transmission of the second part of the first TB on at leastone of the PUSCH resources. In response to receiving the uplinkpre-emption indication, the wireless device may restart thebwp-InactivityTimer. In an example, during a time period when thebwp-InactivityTimer is running, the wireless device may monitor a PDCCHon the first BWP. The wireless device may receive a second DCIcomprising a second uplink grant. In response to receiving the secondDCI, the wireless device may restart the bwp-InactivityTimer, and startuplink transmission (a retransmission of the first TB, or an initialtransmission of a second TB) based on the second uplink grant. Exampleembodiments, by restarting the bwp-InactivityTimer when receiving anuplink pre-emption indication, may avoid unnecessary BWP switch to adefault BWP. Example embodiments may improve data transmission delay,and/or system throughput.

Similarly, the example embodiments may apply to management of aSCellDeactivationTimer. In an example, when receiving a DCI comprisingan uplink grant on an activated SCell, a wireless device may start theSCellDeactivationTimer with an initial value. The wireless device maystart an uplink transmission on the uplink grant before receiving anuplink pre-emption indication. In response to receiving the uplinkpre-emption indication, the wireless device may stop the ongoing uplinktransmission on the uplink grant. In response to receiving the uplinkpre-emption indication, the wireless device may restart theSCellDeactivationTimer. When the SCellDeactivationTimer is running, thewireless device may keep the SCell in active state. The wireless devicemay monitor a PDCCH on(or for) the SCell for detecting a second DCI fora second uplink grant. Upon receiving the second uplink grant, thewireless device may perform uplink transmission on the second uplinkgrant. Example embodiments, by restarting the SCellDeactivationTimerwhen receiving an uplink pre-emption indication, may avoid unnecessarySCell deactivation. Example embodiments may improve data transmissiondelay, and/or system throughput.

FIG. 36 shows an example of improved BWP state management. In anexample, a base station (e.g., gNB in FIG. 36) may transmit to awireless device (e.g., UE in FIG. 36) a first DCI comprising a firstuplink grant. In response to receiving the first DCI, the wirelessdevice may start a BWP inactivity timer (e.g., bwp-InactivityTimer) withan initial timer value. The initial timer value may be indicated in anRRC message. The wireless device may keep a first BWP in active statewhen the bwp-InactivityTimer is running.

As shown in FIG. 36, the wireless device may receive an uplinkpre-emption indication from the base station, before the wireless devicestarts a transmission of a first TB on PUSCH resources of the uplinkgrant. The uplink pre-emption indication may indicate that the wirelessdevice may cancel (suspend, or stop) a scheduled transmission of thefirst TB on at least one of the PUSCH resources. In response to theuplink pre-emption indication, the physical layer may cancel thescheduled transmission of the first TB on the at least one of the PUSCHresources of the uplink grant. In response to receiving the uplinkpre-emption indication, the wireless device may restart thebwp-InactivityTimer. In an example, during a time period when thebwp-InactivityTimer is running, the wireless device may monitor a PDCCHon the first BWP. The wireless device may receive a second DCIcomprising a second uplink grant. In response to receiving the secondDCI, the wireless device may restart the bwp-InactivityTimer, and startuplink transmission (a retransmission of the first TB, or an initialtransmission of a second TB) based on the second uplink grant. Exampleembodiments, by restarting the bwp-InactivityTimer when receiving anuplink pre-emption indication, may avoid unnecessary BWP switch to adefault BWP. Example embodiments may improve data transmission delay,and/or system throughput.

Similarly, the example embodiments may apply to management of aSCellDeactivationTimer. In an example, when receiving a DCI comprisingan uplink grant on an activated SCell, a wireless device may start theSCellDeactivationTimer with an initial value. The wireless device mayreceive an uplink pre-emption indication before the wireless devicestarts an uplink transmission on the uplink grant. In response toreceiving the uplink pre-emption indication, the wireless device maycancel the scheduled (e.g., not started yet) uplink transmission on theuplink grant. In response to receiving the uplink pre-emptionindication, the wireless device may restart the SCellDeactivationTimer.When the SCellDeactivationTimer is running, the wireless device may keepthe SCell in active state. The wireless device may monitor a PDCCH on(or for) the SCell for detecting a second DCI for a second uplink grant.Upon receiving the second uplink grant, the wireless device may performuplink transmission on the second uplink grant. Example embodiments, byrestarting the SCellDeactivationTimer when receiving an uplinkpre-emption indication, may avoid unnecessary SCell deactivation.Example embodiments may improve data transmission delay, and/or systemthroughput.

In existing DRX operation, a wireless device, when configured with a DRXoperation, may start a DRX inactivity timer (e.g., drx-InactivityTimer),when the wireless device receives a DCI comprising an uplink grant.During a time period when the drx-InactivityTimer is running, thewireless device may stay in a DRX Active Time during which the wirelessdevice may monitor PDCCH and/or receive data packet on PDSCH. When thedrx-InactivityTimer expires, the wireless device may switch to a DRXoff/sleep mode (e.g., not in DRX Active Time), during which the wirelessdevice may stop monitoring PDCCH and/or stop receiving data packet onPDSCH, e.g., for the purpose of saving power consumption. In an example,the wireless device may start uplink transmission based on the uplinkgrant before the wireless device receives an uplink pre-emptionindication. The wireless device may stop the ongoing uplink transmissionin response to the uplink pre-emption indication. The wireless devicemay be expecting to receive a second DCI for uplink retransmission. Thedrx-InactivityTimer may expires after the wireless device receives theuplink pre-emption indication, and/or when the wireless device isexpecting to receive the second DCI for the retransmission. The wirelessdevice, by implementing existing technologies, may switch to the DRXoff/sleep mode, in response to an expiry of the drx-InactivityTimer.Existing technologies may increase data transmission delay, and/orreduce system throughput. There is a need to improve DRX operation whena wireless device receives an uplink pre-emption indication. Exampleembodiments may avoid switching to the DRX off/sleep mode, after thewireless device receives the uplink pre-emption indication. Exampleembodiments may improve data transmission delay and/or systemthroughput.

FIG. 37 shows an example of improved DRX operation. In an example, abase station (e.g., gNB in FIG. 37) may transmit to a wireless device(e.g., UE in FIG. 37) one or more RRC messages comprising configurationparameters of a DRX operation. The wireless device may activate the DRXoperation based on the configuration parameters, by employing one ormore examples of FIG. 24 and/or FIG. 25. The gNB may transmit to thewireless device a first DCI comprising a first uplink grant. In responseto receiving the first DCI, the wireless device may start a DRXinactivity timer (e.g., drx-InactivityTimer) with an initial timervalue. The initial timer value may be indicated in an RRC message. Thewireless device may maintain in a DRX Active Time when thedrx-InactivityTimer is running.

As shown in FIG. 37, based on an uplink grant comprised in the firstDCI, the wireless device may start an initial (or a new) transmission onPUSCH resources on an active BWP (or an active cell). In an example, asshown in FIG. 37, the wireless device may receive an uplink pre-emptionindication from the base station, during a transmission of a first TB onPUSCH resources of the uplink grant. The uplink pre-emption indicationmay indicate that the wireless device may stop (suspend, or cancel) thetransmission of the first TB on at least one of the PUSCH resources. Inresponse to the uplink pre-emption indication, the physical layer maystop the ongoing transmission of the first TB on the at least one of thePUSCH resources of the uplink grant. In an example, the physical layermay finish a transmission of a first part of the first TB and may notstart a transmission of a second part of the first TB, when the wirelessdevice receives the uplink pre-emption indication. The uplinkpre-emption indication may indicate that the wireless device may stop(suspend, or cancel) the transmission of the second part of the first TBon at least one of the PUSCH resources. In response to receiving theuplink pre-emption indication, the wireless device may restart thedrx-InactivityTimer. In an example, during a time period when thedrx-InactivityTimer is running, the wireless device may monitor a PDCCHon the active BWP (or the active cell). The wireless device may receivea second DCI comprising a second uplink grant. In response to receivingthe second DCI, the wireless device may restart the drx-InactivityTimer,and/or start uplink transmission (a retransmission of the first TB, oran initial transmission of a second TB) based on the second uplinkgrant. Example embodiments, by restarting the drx-InactivityTimer whenreceiving an uplink pre-emption indication, may avoid unnecessaryswitching from DRX Active Time to DRX off/sleep mode. Exampleembodiments may improve data transmission delay, and/or systemthroughput.

In an example, example embodiments of FIG. 31 may be applied to improveHARQ process when out-of-order HARQ is supported by a wireless device,or when the wireless device receives an out-of-order uplink grant. FIG.38 shows an example embodiment of improved HARQ process whenout-of-order HARQ is supported.

In an example, when out-of-order HARQ is supported by a base stationand/or a wireless device, a base station, after transmitting a first DCIindicating a first uplink grant on a BWP or a cell, may transmit asecond DCI indicating a second uplink grant on the BWP or the cell,before a wireless device start an uplink transmission via the firstuplink grant. In an example, the second DCI may be referred to as anout-of-order uplink grant. In an example, a transmission via the seconduplink grant may be more urgent or require less latency than atransmission via the first uplink grant. In an example, a transmissionoccasion via the second uplink grant may be earlier in time domain thana transmission occasion via the first uplink grant.

In an example, as shown in FIG. 38, a base station (e.g., gNB in FIG.38) may transmit to a wireless device (e.g., UE in FIG. 38) a first DCIcomprising a first uplink grant. The first uplink grant may comprisingparameters of first time domain resource allocation. In an example, thewireless device may create (or generate) a first TB and prepare anuplink transmission for the first TB via the first uplink grant. In anexample, after transmitting the first DCI, the base station may transmita second DCI comprising a second uplink grant, before a PUSCHtransmission occasion indicated by the first DCI. In an example, thewireless device may create (or generate) a second TB and prepare anuplink transmission for the second TB via the second uplink grant. Thesecond uplink grant may comprise parameters of second time domainresource allocation. In an example, a PUSCH transmission occasionindicated by the second DCI may be earlier than a PUSCH transmissionoccasion indicated by the first DCI. In an example, a first HARQ processnumber indicated in the first DCI may be same as or different from asecond HARQ process number indicated in the second DCI.

In an example, as shown in FIG. 38, in response to the first DCI and/orthe second DCI, the wireless device may transmit the second TB via thesecond uplink grant. In an example, the wireless device may not transmitthe first TB via the first uplink grant, after transmitting the secondTB via the second uplink grant, e.g., due to processing capability ofthe wireless device. In an example, the wireless device may drop atransmission of the first TB via the first uplink grant. In an example,the wireless device, in response to dropping the transmission of thefirst TB, may flush a HARQ buffer associated with a HARQ processidentified by a HARQ process number indicated in the first DCI. Thewireless device may consider the transmission of the first TB as hasbeen performed. The wireless device may store an NDI value received inthe first DCI as a current NDI value for a HARQ process number indicatedin the first DCI. The wireless device may perform a retransmission ofthe first TB based the stored NDI value and a new NDI value received ina third DCI comprising a same HARQ process number as the one received inthe first DCI.

In an example, a wireless device may be capable of processingout-of-order HARQ (or out-of-order uplink grant). The wireless device,if capable of processing out-of-order HARQ, may process a second uplinkgrant, after receiving a first uplink grant and before a transmissionvia the first uplink grant. The wireless device may transmit an uplinkTB via the second uplink grant, after processing the second uplinkgrant. The wireless device may or may not transmit another uplink TB viathe first uplink grant, after the transmission via the second uplinkgrant. In an example, a wireless device may not be capable of processingout-of-order HARQ. The wireless device, if not capable of processingout-of-order HARQ, may not process a second uplink grant, afterreceiving a first uplink grant and before a transmission via the firstuplink grant.

FIG. 39 shows an example embodiment of improved HARQ processing when awireless device supports out-of-order HARQ. In an example, a wirelessdevice may transmit one or more capability parameters of out-of-orderHARQ (or out-of-order grant) processing to a base station. The one ormore capability parameters may be transmitted in an RRC message (e.g.,UE-NR-Capability IE, or UECapabilityInformation message), e.g., as aresponse to a capability request message transmitted by a base station.The one or more capability parameters may comprises: a HARQ processingindicator indicating whether out-of-order HARQ (or out-of-order uplinkgrant) is supported or not; and/or a value of a time period (or a timeoffset). In an example, the wireless device, within the time periodafter receiving a first DCI, may process a second DCI indicating anout-of-order grant. In an example, the wireless device, at a timeearlier than the time offset before a PUSCH transmission occasionindicated in a first DCI, may process a second DCI indicating anout-of-order grant. In an example, based on the one or more capabilityparameters, the base station may transmit to the wireless device one ormore RRC messages comprising parameters of PDCCH monitoring based on theone or more capability parameters. In an example, when the one or morecapability parameters indicates that the wireless device is capable ofprocessing out-of-order HARQ, the parameters of PDCCH monitoring maycomprise a first RNTI value (e.g., C-RNTI) for a reception of normaldynamic uplink grant (e.g., dedicated for eMBB transmission); a secondRNTI value (e.g., C2-RNTI) for a reception of out-of-order uplink grant(e.g., dedicated for URLLC transmission). In an example, in response toreceiving the one or more RRC messages, the wireless device, afterreceiving a first DCI indicating a first uplink grant, may monitor PDCCHfor a second DCI indicating a second uplink grant, based on theparameters of PDCCH monitoring. The wireless device may monitor thePDCCH for the second DCI by attempting to decode the second DCI with thesecond RNTI value. The wireless device may monitor the PDCCH for thesecond DCI with a monitoring periodicity indicated by the parameters ofPDCCH monitoring.

In an example, before starting uplink transmission via the first uplinkgrant indicated by the first DCI, the wireless device may receive thesecond DCI indicating the second uplink grant during monitoring thePDCCH for the second DCI. The second uplink grant may occur earlier thanthe first uplink grant. The wireless device may transmit a second uplinkTB via the second uplink grant, in response to the second DCI. In anexample, the wireless device, after transmitting the second uplink TB,may resume a transmission of the first TB via the first uplink grantindicated by the first DCI. In an example, the wireless device, aftertransmitting the second uplink TB, may drop a transmission of the firstTB via the first uplink grant indicated by the first DCI. In an example,the wireless device, after transmitting the second uplink TB, maydetermine, based on the capability parameters, whether the wirelessdevice may resume a transmission of the first TB via the first uplinkgrant or the wireless device may drop the transmission of the first TB.In an example, when a time offset, between a first time after thewireless finishes the transmission of the second uplink TB and a secondtime before a first PUSCH transmission occasion indicated in the firstDCI, is greater than the time offset indicated by the capabilityparameters, the wireless device may resume the transmission of the firstTB via the first uplink grant. In an example, when a first time offset,between a first time after the wireless finishes the transmission of thesecond uplink TB and a second time before a first PUSCH transmissionoccasion indicated in the first DCI, is smaller than a second timeoffset indicated by the capability parameters, the wireless device maydrop the transmission of the first TB via the first uplink grant. In anexample, when a first time offset, between a first time when thewireless device receives the first DCI and a second time when thewireless device receives the second DCI, is less than a second timeoffset indicated by the capability parameters, the wireless device mayresume the transmission of the first TB via the first uplink grant. Inan example, when a first time offset, between a first time when thewireless device receives the first DCI and a second time when thewireless device receives the second DCI, is greater than a second timeoffset indicated by the capability parameters, the wireless device maydrop the transmission of the first TB via the first uplink grant.

In an example, a wireless device may receive a first DCI comprising afirst uplink radio resource and a first NDI value. The wireless devicemay create (or generate) a first TB in response to the first DCI. In anexample, the wireless device may receive a second DCI comprising asecond uplink radio resource. The wireless device, in response to thesecond DCI, may transmit a second TB via the second uplink radioresource and drop a transmission of the first TB on the first uplinkradio resource. In an example, the first uplink radio resource may notoverlap with the second uplink radio resource. In an example, the seconduplink radio resource may be earlier in time than the first uplink radioresource. The wireless device may receive a third DCI comprising a thirduplink radio resource and a third NDI value. the wireless device mayretransmit the first TB on the third uplink radio resource based on thefirst NDI value and the second NDI value.

In an example, a wireless device may transmit one or more capabilityparameters of processing out-of-order uplink grant. The wireless devicemay receive one or more configuration parameters of PDCCH monitoring.The one or more configuration parameters may comprise a first RNTI valuefor a reception of a first type of dynamic uplink grant. The one or moreconfiguration parameters may comprise a second RNTI value for areception of a second type of dynamic uplink grant, based on the one ormore capability parameters. The second type of dynamic uplink grant maycomprise an out-of-order uplink grant. The wireless device may receive afirst DCI comprising a first uplink radio resource and a first NDIvalue. The wireless device may create a first TB in response to thefirst DCI. The wireless device may monitor PDCCH for the reception ofthe second type of dynamic uplink grant based on the second RNTI value.The wireless device may receive a second DCI comprising the second typeof dynamic uplink grant. The wireless device may transmit a second TBvia the second type of dynamic uplink grant, in response to the secondDCI.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of base stations or a plurality ofwireless devices in a coverage area that may not comply with thedisclosed methods, for example, because those wireless devices or basestations perform based on older releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments.

If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state.

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (i.e.hardware with a biological element) or a combination thereof, all ofwhich may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device. Theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

1. A method comprising: receiving, by a wireless device from a basestation, a first uplink grant, for a first transport block (TB) of ahybrid acknowledgment repeat request (HARQ) process; cancelling anuplink transmission of the first TB of the HARQ process based onreceiving a pre-emption indication indicating cancellation oftransmission via one or more uplink resources indicated by the firstuplink grant; determining, after cancelling the uplink transmission ofthe first TB of the HARQ process, that a received second uplink grant isused for a new transmission of a second TB associated with the HARQprocess; and transmitting, by the wireless device to the base station,the second TB of the HARQ process based on the determining.
 2. Themethod of claim 1, wherein a first new data indicator associated withthe first uplink grant comprises a first value.
 3. The method of claim2, further comprising: storing, by the wireless device, the first valueof the first uplink grant; and maintaining, by the wireless device, thefirst value after cancelling the uplink transmission indicated by thefirst uplink grant.
 4. The method of claim 2, wherein a second new dataindicator associated with the second uplink grant comprises a secondvalue different from the first value.
 5. The method of claim 4, furthercomprising determining that a new data indication of the HARQ process istoggled based on the second value being different from the first value.6. The method of claim 5, wherein the transmitting the second TB of theHARQ process is based on the new data indication being toggled.
 7. Themethod of claim 1, wherein the second TB is different from the first TB.8. The method of claim 1, wherein the transmitting of the second TB isan initial transmitting of the second TB.
 9. The method of claim 1,wherein the first uplink grant is included in a first downlink controlinformation comprising a process identifier of the HARQ process.
 10. Themethod of claim 9, wherein the second uplink grant is included in asecond downlink control information comprising the process identifier ofthe HARQ process.
 11. A wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receive, from abase station, a first uplink grant for a first transport block (TB) of ahybrid acknowledgment repeat request (HARQ) process; cancel an uplinktransmission of the first TB of the HARQ process based on receiving apre-emption indication indicating cancellation of transmission via oneor more uplink resources indicated by the first uplink grant; determine,after cancelling the uplink transmission of the first TB of the HARQprocess, that a received second uplink grant is used for a newtransmission of a second TB associated with the HARQ process; andtransmit, by the wireless device to the base station, the second TB ofthe HARQ process based on the determining.
 12. The method of claim 11,wherein a first new data indicator associated with the first uplinkgrant comprises a first value.
 13. The method of claim 12, furthercomprising: storing, by the wireless device, the first value of thefirst uplink grant; and maintaining, by the wireless device, the firstvalue after cancelling the uplink transmission indicated by the firstuplink grant.
 14. The method of claim 12, wherein a second new dataindicator associated with the second uplink grant comprises a secondvalue different from the first value.
 15. The method of claim 14,further comprising determining that a new data indication of the HARQprocess is toggled based on the second value being different from thefirst value.
 16. The method of claim 15, wherein the transmitting thesecond TB of the HARQ process is based on the new data indication beingtoggled.
 17. The method of claim 11, wherein the second TB is differentfrom the first TB.
 18. The method of claim 11, wherein the transmittingof the second TB is an initial transmitting of the second TB.
 19. Themethod of claim 11, wherein: the first uplink grant is included in afirst downlink control information comprising a process identifier ofthe HARQ process; and the second uplink grant is included in a seconddownlink control information comprising the process identifier of theHARQ process.
 20. A system comprising: a base station comprising: one ormore processors and memory storing instructions that, when executed bythe one or more processors, cause the base station to: transmit, to awireless device, a first uplink grant for a first transport block (TB)of a hybrid acknowledgment repeat request (HARQ) process; transmit, tothe wireless device, a pre-emption indication indicating cancellation oftransmission via one or more uplink resources indicated by the firstuplink grant; transmit, to the wireless device, a second uplink grantfor a second TB of the HARQ process; and receive, from the wirelessdevice, the second TB of the HARQ process; and the wireless device,wherein the wireless device comprises: one or more processors and memorystoring instructions that, when executed by the one or more processors,cause the wireless device to: receive, from the base station, the firstuplink grant for the first TB; cancel an uplink transmission of thefirst TB of the HARQ process based on receiving the pre-emptionindication; determine, after cancelling the uplink transmission of thefirst TB of the HARQ process, that a received second uplink grant isused for a new transmission of a second TB associated with the HARQprocess; and transmit, by the wireless device to the base station, thesecond TB of the HARQ process based on the determining.